Qlik Sense SAML Integration fails with 500 Internal Server Error, Unanticipated ComponentSpace.SAML2.Exceptions.SAMLBindingException

Bastien_Laugiero — Tue, 16 Nov 2021 11:32:39 GMT

Setting up SAML with Qlik Sense Enterprise on Windows fails.

Accessing the Hub leads to a 500 Internal Server Error

The Qlik Sense Proxy logs (default: C:\Programdata\Qlik\Sense\Log\Proxy\Trace\xxx_Audit.log) shows:

Unanticipated ComponentSpace.SAML2.Exceptions.SAMLBindingException occurred for connection

Resolution:

Create new IDP Metadata to change the binding method for the SAML Request to HTTP Redirect instead.

If using new SHA256 certificates ensure the conversion was performed. SHA-256 and Converting the Cryptographic Service Provider Type

Example:

<md:SingleSignOnService Location="https://server/MiddlewareRestServices/extension/SS0" Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect"/>

Cause:

This error might indicate that the HTTP method you use to bind for SAML authentication requests in your IDP Metadata is not supported.

Only HTTP Redirect is currently supported so if you use HTTP POST instead you will get this error.

More details are available on our online documentation: Authentication solutions

article Qlik Sense SAML Integration fails with 500 Internal Server Error, Unanticipated ComponentSpace.SAML2.Exceptions.SAMLBindingException in Official Support Articles

Qlik Sense SAML Integration fails with 500 Internal Server Error, Unanticipated ComponentSpace.SAML2.Exceptions.SAMLBindingException

Resolution:

Cause: