|
Cannot SLO from SP
|
|
3
|
19
|
May 7, 2025
|
|
Unable to load SAML.config file
|
|
1
|
4
|
May 7, 2025
|
|
Json configuration fails validation
|
|
5
|
22
|
April 7, 2025
|
|
Idp Initiated SSO and send via HTTP POST
|
|
1
|
24
|
March 18, 2025
|
|
Audience restriction doesn't match
|
|
3
|
17
|
March 14, 2025
|
|
On Azure: System.Security.Cryptography.CryptographicException: The system cannot find the file specified
|
|
6
|
39
|
January 29, 2025
|
|
Reading certificate from Azure Key Vault - Error: no private key
|
|
3
|
23
|
January 15, 2025
|
|
RelayState not getting used
|
|
1
|
30
|
December 19, 2024
|
|
Receiving an SSO response from a partner identity provider has failed
|
|
1
|
69
|
November 22, 2024
|
|
DotNet Core migration 2.1
|
|
9
|
79
|
October 17, 2024
|
|
The SAML response destination ... doesn't match the expected destination ...
|
|
12
|
173
|
August 21, 2024
|
|
The SAML response isn't signed after upgrading from version 2.6 to 7.0
|
|
5
|
74
|
August 13, 2024
|
|
Method to Import User Attributes for User table
|
|
3
|
40
|
June 24, 2024
|
|
Idp Initiated SSO + HTTP POST
|
|
1
|
149
|
June 6, 2024
|
|
Global Authentication
|
|
5
|
147
|
May 28, 2024
|
|
A SAML message cannot be received as the HTTP request is unrecognized
|
|
1
|
145
|
May 25, 2024
|
|
A SAML authn request was expected. Instead samlp:Response was received
|
|
1
|
173
|
May 25, 2024
|
|
SP not redirecting to idp and no error being generated at SP side
|
|
0
|
27
|
May 20, 2024
|
|
Is Multi-Tenancy best option for handling domain name switch?
|
|
5
|
146
|
April 24, 2024
|
|
An SP-initiated SAML response from https://sts.windows.net/xxxxxx was received unexpectedly.
|
|
11
|
458
|
February 8, 2024
|
|
ComponentSpace.SAML2.Exceptions.SAMLEnvironmentException: There is no HTTP context.
|
|
5
|
155
|
January 29, 2024
|
|
ERROR Receiving an SSO response from a partner identity provider has failed
|
|
1
|
219
|
January 25, 2024
|
|
partner identity provider xxxxxxxxxxx is not configured
|
|
1
|
539
|
January 23, 2024
|
|
An error SAML response status was received. urn:oasis:names:tc:SAML:2.0:status:Responder: An error occurred.
|
|
1
|
177
|
January 8, 2024
|
|
How to set the "AssertionConsumerServiceUrl" dynamically where the application key is unique for each logged in user
|
|
9
|
116
|
November 21, 2023
|
|
An x509 certificate for the local identity provider hasn't been configured
|
|
8
|
173
|
November 21, 2023
|
|
Query about SAML 2.0 SSO for ASP.NET Library Compatibility with FIPS (Federal Information Processing Standard) 140-2
|
|
7
|
117
|
November 8, 2023
|
|
The SAML response isn't signed
|
|
10
|
119
|
October 12, 2023
|
|
ComponentSpace.SAML2.Exceptions.SAMLSchemaValidationException: 'One or more configuration XML schema validation errors occurred.'
|
|
3
|
167
|
October 2, 2023
|
|
Failed to verify the XML signature
|
|
1
|
200
|
September 19, 2023
|