Receiving an SSO response from a partner identity provider has failed

[ComponentSpace]

It looks like there’s an issue loading the PFX file used to decrypt the SAML assertion. We use the X509Certificate2 class to load PFX files.

Please take a look at:

Troubleshooting Loading X.509 Certificates

When loading X.509 certificates using the .NET X509Certificate2 class, always specify the X509KeyStorageFlags.MachineKeySet flag. This ensures the certificate may be accessed from within IIS. For example: X509Certificate2 x509Certificate = new X509Certificate2(“idp.pfx”, “password”, X509KeyStorageFlags.MachineKeySet); Certificates Stored in Files When loading a certificate from file, if an access denied exception occurs, this gen…

Make sure the file permissions are set correctly. The account under which the application runs must have read access to the PFX file and create permission for the private key container folder.

If running under IIS, check that Load User Profile is set to true for the application pool under which your application is running.

If there’s still an issue, please enable SAML trace and send the generated log file as an email attachment to support@componentspace.com.

Enabling SAML for ASP.NET Core Trace

SAML debug trace may be enabled to assist with tracking down issues. The standard ASP.NET Core logging API is used. In our examples, we make use of Serilog. However, any logging provider, including Serilog, Log4Net and NLog, may be used to capture the logging information. Regardless of the logging provider used, the “Debug” level must be specified for “ComponentSpace”. "Logging": { "LogLevel": { "Default": "Information", "Microsoft": "Warning", "Microsoft.Hosting.Lifetime": "Inf…