Service Provider delay while attempting SAML Artifact Binding

    Applies to:
  • SecureAuth Identity Platform
  • Legacy SecureAuth IdP
Deployment model:
  • Hybrid
  • On Premises
  • Version Affected:  9.2 and higher


    When SAML metadata has been shared by a realm with a Service Provider, some Service Providers can attempt SAML Artifact Binding instead of HTTP Post Binding or HTTP Redirect Binding.  This typically causes a delay while the Service Provider times out.



    The metadata shared by a realm includes an AttributeAuthorityDescriptor with a SOAP binding.

    SecureAuth IdP does not currently have SAML SOAP support.



    Edit the metadata XML before sharing with the Service Provider. 

    Remove the entire AttributeAuthorityDescriptor section including everything within e.g.:





    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


    • Should the Location Bindings using SOAP also be removed from the metadata?

      Comment actions Permalink
    • Would you mind opening a ticket Pete to discuss further?

      Comment actions Permalink

    Please sign in to leave a comment.