|
An error SAML response status was received. urn:oasis:names:tc:SAML:2.0:status:Responder: An error occurred.
|
|
1
|
145
|
January 8, 2024
|
|
An SP-initiated SAML response from Identity Provider was received unexpectedly.
|
|
15
|
271
|
December 28, 2023
|
|
AbstractSamlConfigurationResolver related issue
|
|
3
|
95
|
December 13, 2023
|
|
An x509 certificate for the local identity provider hasn't been configured
|
|
8
|
143
|
November 21, 2023
|
|
Read the certificate from Azure key vault and SP authentication scenario
|
|
3
|
109
|
November 21, 2023
|
|
Query about SAML 2.0 SSO for ASP.NET Library Compatibility with FIPS (Federal Information Processing Standard) 140-2
|
|
7
|
113
|
November 8, 2023
|
|
An unhandled exception occurred while processing the request.
|
|
3
|
86
|
October 27, 2023
|
|
The SAML response isn't signed
|
|
10
|
104
|
October 12, 2023
|
|
SSO Logout Request does not contain signature as query parameter
|
|
9
|
76
|
October 4, 2023
|
|
ComponentSpace.SAML2.Exceptions.SAMLSchemaValidationException: 'One or more configuration XML schema validation errors occurred.'
|
|
3
|
114
|
October 2, 2023
|
|
Issues storing tenant(s) configuration on database
|
|
1
|
66
|
October 2, 2023
|
|
Failed to verify the XML signature
|
|
1
|
187
|
September 19, 2023
|
|
Dependency Injection Test Failed on 'There is no HTTP context,'
|
|
1
|
82
|
September 11, 2023
|
|
Users couldn't view the switch accounts options when they try to login.
|
|
5
|
50
|
September 1, 2023
|
|
Acting as IDP > SAMLResponse isn't signed
|
|
1
|
81
|
August 28, 2023
|
|
Migrating to new Web server; nothing happens after initiation of SSO to partner IDP
|
|
1
|
57
|
August 19, 2023
|
|
Storing certificates in Azure Key Vault
|
|
7
|
98
|
August 7, 2023
|
|
Attached InResponseTo attribute into the IDP Response
|
|
5
|
86
|
August 6, 2023
|
|
A local service provider is not configured.
|
|
5
|
105
|
July 21, 2023
|
|
MachineKeys permission settings preventing RDP certificate renewal
|
|
1
|
47
|
June 26, 2023
|
|
ComponentSpace.Saml2.Exceptions.SamlBindingException: A SAML message cannot be received as the HTTP request is unrecognized.
|
|
1
|
213
|
May 22, 2023
|
|
HTTP request is unrecognized Error
|
|
4
|
86
|
May 22, 2023
|
|
The SAML response signature failed to verify
|
|
5
|
152
|
May 15, 2023
|
|
Client Credential flow with JWT private key assertion failing
|
|
1
|
69
|
March 31, 2023
|
|
The logout response isn't signed - Error
|
|
1
|
49
|
March 27, 2023
|
|
Getting this exception: An error SAML response status was received. urn:oasis:names:tc:SAML:2.0:status:Responder
|
|
1
|
80
|
March 27, 2023
|
|
"Invalid Provider Type Specified" Exception Error
|
|
3
|
56
|
February 16, 2023
|
|
"Unexpected Token" Error on InitiateSSO()
|
|
6
|
67
|
February 8, 2023
|
|
"Failed to verify signature on HTTP redirect message" on ReceiveLogoutMessageByHTTPRedirect
|
|
6
|
65
|
January 31, 2023
|
|
SLO request results in Azure error: "session index does not match the existing sessions"
|
|
3
|
95
|
January 12, 2023
|