Sign SAML Assertion vs Sign SAML Message

    Applies to:
  • Legacy SecureAuth IdP
Deployment model:
  • On Premises
  • SecureAuth IdP Version Affected: All

    Description: There is a requirement from the Service Provider to have the signature element within the Assertion tab, instead of outside of it.

    Cause: By default, our settings do not sign the SAML assertion, but sign the SAML message.

    Resolution: Change the dropdown for sign SAML Assertion to True.  (The message can remain true as well, but it depends on if the SP accepts the signature in the assertion twice or not.)

    SAML Assertion with Message Signing:

    The Assertion tags do not contain the x509 Certificate


    SAML Assertion with Assertion Signed:

    x509Certificate is within the SAML assertion tags


    SecureAuth Knowledge Base Articles provide information based on specific use cases and may not apply to all appliances or configurations. Be advised that these instructions could cause harm to the environment if not followed correctly or if they do not apply to the current use case.

    Customers are responsible for their own due diligence prior to utilizing this information and agree that SecureAuth is not liable for any issues caused by misconfiguration directly or indirectly related to SecureAuth products.

    0 out of 0 found this helpful



    Please sign in to leave a comment.