I want to migrate an old SAML setup to Component space but I'm getting a forbidden request error with my new component space
|
|
1
|
28
|
September 17, 2024
|
Store SAML Configuration in MYSQL database
|
|
1
|
22
|
September 6, 2024
|
The SAML response destination ... doesn't match the expected destination ...
|
|
12
|
179
|
August 21, 2024
|
Struggling with SAML Configuration—Need Advice!
|
|
1
|
77
|
August 20, 2024
|
The SAML response isn't signed after upgrading from version 2.6 to 7.0
|
|
5
|
79
|
August 13, 2024
|
How to change PartnerServiceProviderConfigurations dynamically before SSO and SLO
|
|
4
|
178
|
August 12, 2024
|
Issue with SSL Certificate Configuration on IIS
|
|
1
|
83
|
July 22, 2024
|
KeyCloak - ComponentSpace.Saml2 version 2.8.7.0
|
|
1
|
96
|
June 6, 2024
|
An SP-initiated SAML response from was received unexpectedly
|
|
3
|
331
|
June 6, 2024
|
Idp Initiated SSO + HTTP POST
|
|
1
|
152
|
June 6, 2024
|
ISsoOptions Destination option is ignored during Authn Request initiated by SP
|
|
1
|
89
|
May 26, 2024
|
SP is not redirecting to IdP SSO url
|
|
8
|
163
|
May 26, 2024
|
A SAML message cannot be received as the HTTP request is unrecognized
|
|
1
|
153
|
May 25, 2024
|
A SAML authn request was expected. Instead samlp:Response was received
|
|
1
|
179
|
May 25, 2024
|
ReceiveSSO throws error while authenticating with ADFS (SAML 2.0) running on AWS EKS
|
|
11
|
180
|
May 22, 2024
|
Specifying other variables for HttpPostFormOptions during run time
|
|
4
|
110
|
May 17, 2024
|
Unusual Response Signature validation issue (PingFederate)
|
|
5
|
225
|
May 10, 2024
|
Is Multi-Tenancy best option for handling domain name switch?
|
|
5
|
146
|
April 24, 2024
|
How to SLO with Mutliple IdP configurations
|
|
1
|
148
|
April 24, 2024
|
SSO User State Management
|
|
8
|
167
|
February 27, 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
|
266
|
February 22, 2024
|
Entity Id usage
|
|
8
|
158
|
February 13, 2024
|
An SP-initiated SAML response from https://sts.windows.net/xxxxxx was received unexpectedly.
|
|
11
|
504
|
February 8, 2024
|
Does PartnerName is mandatory to pass in _samlServiceProvider.InitiateSsoAsync() & PartnerIdentityProviderConfiguration
|
|
1
|
148
|
February 7, 2024
|
ComponentSpace.SAML2.Exceptions.SAMLEnvironmentException: There is no HTTP context.
|
|
5
|
166
|
January 29, 2024
|
partner identity provider xxxxxxxxxxx is not configured
|
|
1
|
547
|
January 23, 2024
|
PartnerCertificates in PartnerProviderConfiguration can handle both expired and non-expired certificates
|
|
20
|
174
|
January 23, 2024
|
Connection Refused / Secure Connection Failed
|
|
7
|
176
|
January 12, 2024
|
An error SAML response status was received. urn:oasis:names:tc:SAML:2.0:status:Responder: An error occurred.
|
|
1
|
184
|
January 8, 2024
|
An SP-initiated SAML response from Identity Provider was received unexpectedly.
|
|
15
|
314
|
December 28, 2023
|