|
The SAML response isn't signed after upgrading from version 2.6 to 7.0
|
|
5
|
96
|
August 13, 2024
|
|
Issue with Decrypting the SAML Assertion
|
|
7
|
103
|
August 5, 2024
|
|
Error in Payload
|
|
1
|
22
|
July 31, 2024
|
|
SP Initiated SSO + use extentions to pass attributes
|
|
1
|
21
|
July 31, 2024
|
|
Idp Initiated SSO + HTTP POST
|
|
1
|
162
|
June 6, 2024
|
|
SP is not redirecting to IdP SSO url
|
|
8
|
178
|
May 26, 2024
|
|
A SAML message cannot be received as the HTTP request is unrecognized
|
|
1
|
158
|
May 25, 2024
|
|
A SAML authn request was expected. Instead samlp:Response was received
|
|
1
|
184
|
May 25, 2024
|
|
ReceiveSSO throws error while authenticating with ADFS (SAML 2.0) running on AWS EKS
|
|
11
|
194
|
May 22, 2024
|
|
SP not redirecting to idp and no error being generated at SP side
|
|
0
|
33
|
May 20, 2024
|
|
Unusual Response Signature validation issue (PingFederate)
|
|
5
|
245
|
May 10, 2024
|
|
MetadataImporter.SaveCertificate() method is missing in ComponentSpace.SAML2.dll
|
|
3
|
109
|
May 9, 2024
|
|
Is Multi-Tenancy best option for handling domain name switch?
|
|
5
|
154
|
April 24, 2024
|
|
How to SLO with Mutliple IdP configurations
|
|
1
|
152
|
April 24, 2024
|
|
AADSTS7500525: There was an XML error in the SAML message. Verify that the XML content of the SAML messages conforms to the SAML protocol specifications.
|
|
1
|
274
|
February 22, 2024
|
|
An SP-initiated SAML response from https://sts.windows.net/xxxxxx was received unexpectedly.
|
|
11
|
538
|
February 8, 2024
|
|
ComponentSpace.SAML2.Exceptions.SAMLEnvironmentException: There is no HTTP context.
|
|
5
|
181
|
January 29, 2024
|
|
ERROR Receiving an SSO response from a partner identity provider has failed
|
|
1
|
234
|
January 25, 2024
|
|
PartnerCertificates in PartnerProviderConfiguration can handle both expired and non-expired certificates
|
|
20
|
179
|
January 23, 2024
|
|
Connection Refused / Secure Connection Failed
|
|
7
|
185
|
January 12, 2024
|
|
An error SAML response status was received. urn:oasis:names:tc:SAML:2.0:status:Responder: An error occurred.
|
|
1
|
197
|
January 8, 2024
|
|
An SP-initiated SAML response from Identity Provider was received unexpectedly.
|
|
15
|
333
|
December 28, 2023
|
|
AbstractSamlConfigurationResolver related issue
|
|
3
|
103
|
December 13, 2023
|
|
An x509 certificate for the local identity provider hasn't been configured
|
|
8
|
194
|
November 21, 2023
|
|
Read the certificate from Azure key vault and SP authentication scenario
|
|
3
|
149
|
November 21, 2023
|
|
Query about SAML 2.0 SSO for ASP.NET Library Compatibility with FIPS (Federal Information Processing Standard) 140-2
|
|
7
|
135
|
November 8, 2023
|
|
An unhandled exception occurred while processing the request.
|
|
3
|
88
|
October 27, 2023
|
|
The SAML response isn't signed
|
|
10
|
128
|
October 12, 2023
|
|
SSO Logout Request does not contain signature as query parameter
|
|
9
|
79
|
October 4, 2023
|
|
ComponentSpace.SAML2.Exceptions.SAMLSchemaValidationException: 'One or more configuration XML schema validation errors occurred.'
|
|
3
|
184
|
October 2, 2023
|