The SAML response signature failed to verify when multiple Idp configurations present
|
|
3
|
5
|
September 10, 2025
|
Adding parameter to redirect request to IdP
|
|
8
|
59
|
July 31, 2025
|
An X.509 signature certificate for the local identity provider hasn't been configured
|
|
3
|
108
|
June 12, 2025
|
Multi-tenancy in implementing ISAMLConfigurationResolver
|
|
4
|
46
|
June 6, 2025
|
Audience restriction doesn't match
|
|
5
|
80
|
May 25, 2025
|
IdP initiated SSO - Failed to send the SAML message over HTTP-Post
|
|
3
|
75
|
May 23, 2025
|
Cannot SLO from SP
|
|
3
|
44
|
May 7, 2025
|
Unable to load SAML.config file
|
|
1
|
45
|
May 7, 2025
|
Json configuration fails validation
|
|
5
|
33
|
April 7, 2025
|
Idp Initiated SSO and send via HTTP POST
|
|
1
|
59
|
March 18, 2025
|
On Azure: System.Security.Cryptography.CryptographicException: The system cannot find the file specified
|
|
6
|
80
|
January 29, 2025
|
Reading certificate from Azure Key Vault - Error: no private key
|
|
3
|
69
|
January 15, 2025
|
RelayState not getting used
|
|
1
|
41
|
December 19, 2024
|
Receiving an SSO response from a partner identity provider has failed
|
|
1
|
112
|
November 22, 2024
|
DotNet Core migration 2.1
|
|
9
|
99
|
October 17, 2024
|
The SAML response destination ... doesn't match the expected destination ...
|
|
12
|
205
|
August 21, 2024
|
The SAML response isn't signed after upgrading from version 2.6 to 7.0
|
|
5
|
96
|
August 13, 2024
|
Method to Import User Attributes for User table
|
|
3
|
45
|
June 24, 2024
|
Idp Initiated SSO + HTTP POST
|
|
1
|
162
|
June 6, 2024
|
Global Authentication
|
|
5
|
156
|
May 28, 2024
|
A SAML message cannot be received as the HTTP request is unrecognized
|
|
1
|
157
|
May 25, 2024
|
A SAML authn request was expected. Instead samlp:Response was received
|
|
1
|
183
|
May 25, 2024
|
SP not redirecting to idp and no error being generated at SP side
|
|
0
|
33
|
May 20, 2024
|
Is Multi-Tenancy best option for handling domain name switch?
|
|
5
|
154
|
April 24, 2024
|
An SP-initiated SAML response from https://sts.windows.net/xxxxxx was received unexpectedly.
|
|
11
|
535
|
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
|
233
|
January 25, 2024
|
partner identity provider xxxxxxxxxxx is not configured
|
|
1
|
565
|
January 23, 2024
|
An error SAML response status was received. urn:oasis:names:tc:SAML:2.0:status:Responder: An error occurred.
|
|
1
|
196
|
January 8, 2024
|
How to set the "AssertionConsumerServiceUrl" dynamically where the application key is unique for each logged in user
|
|
9
|
128
|
November 21, 2023
|