|
Method to Import User Attributes for User table
|
|
3
|
37
|
June 24, 2024
|
|
Idp Initiated SSO + HTTP POST
|
|
1
|
72
|
June 6, 2024
|
|
Global Authentication
|
|
5
|
128
|
May 28, 2024
|
|
A SAML message cannot be received as the HTTP request is unrecognized
|
|
1
|
88
|
May 25, 2024
|
|
A SAML authn request was expected. Instead samlp:Response was received
|
|
1
|
119
|
May 25, 2024
|
|
SP not redirecting to idp and no error being generated at SP side
|
|
0
|
7
|
May 20, 2024
|
|
Is Multi-Tenancy best option for handling domain name switch?
|
|
5
|
129
|
April 24, 2024
|
|
An SP-initiated SAML response from https://sts.windows.net/xxxxxx was received unexpectedly.
|
|
11
|
252
|
February 8, 2024
|
|
ComponentSpace.SAML2.Exceptions.SAMLEnvironmentException: There is no HTTP context.
|
|
5
|
130
|
January 29, 2024
|
|
ERROR Receiving an SSO response from a partner identity provider has failed
|
|
1
|
166
|
January 25, 2024
|
|
partner identity provider xxxxxxxxxxx is not configured
|
|
1
|
471
|
January 23, 2024
|
|
An error SAML response status was received. urn:oasis:names:tc:SAML:2.0:status:Responder: An error occurred.
|
|
1
|
120
|
January 8, 2024
|
|
How to set the "AssertionConsumerServiceUrl" dynamically where the application key is unique for each logged in user
|
|
9
|
82
|
November 21, 2023
|
|
An x509 certificate for the local identity provider hasn't been configured
|
|
8
|
103
|
November 21, 2023
|
|
Query about SAML 2.0 SSO for ASP.NET Library Compatibility with FIPS (Federal Information Processing Standard) 140-2
|
|
7
|
99
|
November 8, 2023
|
|
The SAML response isn't signed
|
|
10
|
85
|
October 12, 2023
|
|
ComponentSpace.SAML2.Exceptions.SAMLSchemaValidationException: 'One or more configuration XML schema validation errors occurred.'
|
|
3
|
73
|
October 2, 2023
|
|
Failed to verify the XML signature
|
|
1
|
166
|
September 19, 2023
|
|
Acting as IDP > SAMLResponse isn't signed
|
|
1
|
64
|
August 28, 2023
|
|
Attached InResponseTo attribute into the IDP Response
|
|
5
|
81
|
August 6, 2023
|
|
Send Signed SAML Response to SP in .net core applications
|
|
10
|
85
|
July 12, 2023
|
|
ComponentSpace.Saml2.Exceptions.SamlBindingException: A SAML message cannot be received as the HTTP request is unrecognized.
|
|
1
|
162
|
May 22, 2023
|
|
Getting this exception: An error SAML response status was received. urn:oasis:names:tc:SAML:2.0:status:Responder
|
|
1
|
55
|
March 27, 2023
|
|
The SAML assertion signature failed to verify
|
|
1
|
184
|
March 8, 2023
|
|
"Invalid Provider Type Specified" Exception Error
|
|
3
|
49
|
February 16, 2023
|
|
The SAML assertion failed to verify and the response isn't signed.
|
|
4
|
126
|
November 18, 2022
|
|
Multiple SAML configurations exist but a configuration name hasn't been specified
|
|
1
|
66
|
November 14, 2022
|
|
SP initiated SSO / Signing Certificate question / https cert expiring
|
|
3
|
103
|
November 7, 2022
|
|
saml.config validation errors
|
|
3
|
50
|
October 28, 2022
|
|
SSO assertion error: The SAML response failed to verify and the assertion isn't signed.
|
|
3
|
128
|
September 13, 2022
|