|
KeyCloak - ComponentSpace.Saml2 version 2.8.7.0
|
|
1
|
130
|
June 6, 2024
|
|
An SP-initiated SAML response from was received unexpectedly
|
|
3
|
436
|
June 6, 2024
|
|
Idp Initiated SSO + HTTP POST
|
|
1
|
217
|
June 6, 2024
|
|
Global Authentication
|
|
5
|
211
|
May 28, 2024
|
|
SP is not redirecting to IdP SSO url
|
|
8
|
310
|
May 26, 2024
|
|
A SAML message cannot be received as the HTTP request is unrecognized
|
|
1
|
201
|
May 25, 2024
|
|
ReceiveSSO throws error while authenticating with ADFS (SAML 2.0) running on AWS EKS
|
|
11
|
304
|
May 22, 2024
|
|
Specifying other variables for HttpPostFormOptions during run time
|
|
4
|
194
|
May 17, 2024
|
|
Unusual Response Signature validation issue (PingFederate)
|
|
5
|
365
|
May 10, 2024
|
|
MetadataImporter.SaveCertificate() method is missing in ComponentSpace.SAML2.dll
|
|
3
|
168
|
May 9, 2024
|
|
Multiple Audiences in AudienceRestrictions not working
|
|
1
|
210
|
April 29, 2024
|
|
Is Multi-Tenancy best option for handling domain name switch?
|
|
5
|
214
|
April 24, 2024
|
|
OpenID for ASP.NET Core v3.5.0 release
|
|
0
|
186
|
February 29, 2024
|
|
SAML for ASP.NET Core v5.0.0 release
|
|
0
|
254
|
February 29, 2024
|
|
SAML for ASP.NET v7.0.0 release
|
|
0
|
272
|
February 29, 2024
|
|
Signature Failure after upgrade to licensed version
|
|
1
|
197
|
March 18, 2024
|
|
SSO User State Management
|
|
8
|
256
|
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
|
432
|
February 22, 2024
|
|
Entity Id usage
|
|
8
|
374
|
February 13, 2024
|
|
An SP-initiated SAML response from https://sts.windows.net/xxxxxx was received unexpectedly.
|
|
11
|
811
|
February 8, 2024
|
|
Does PartnerName is mandatory to pass in _samlServiceProvider.InitiateSsoAsync() & PartnerIdentityProviderConfiguration
|
|
1
|
184
|
February 7, 2024
|
|
Is there any option like RelayStateCache.Add() & RelayState in ASP.net core ?
|
|
1
|
1304
|
January 29, 2024
|
|
ComponentSpace.SAML2.Exceptions.SAMLEnvironmentException: There is no HTTP context.
|
|
5
|
236
|
January 29, 2024
|
|
ERROR Receiving an SSO response from a partner identity provider has failed
|
|
1
|
290
|
January 25, 2024
|
|
PartnerCertificates in PartnerProviderConfiguration can handle both expired and non-expired certificates
|
|
20
|
366
|
January 23, 2024
|
|
Connection Refused / Secure Connection Failed
|
|
7
|
281
|
January 12, 2024
|
|
An error SAML response status was received. urn:oasis:names:tc:SAML:2.0:status:Responder: An error occurred.
|
|
1
|
264
|
January 8, 2024
|
|
Web API to Act As IdP
|
|
3
|
169
|
January 8, 2024
|
|
An SP-initiated SAML response from Identity Provider was received unexpectedly.
|
|
15
|
537
|
December 28, 2023
|
|
AbstractSamlConfigurationResolver related issue
|
|
3
|
147
|
December 13, 2023
|