Citrix Cloud™

Which SAML Binding Mechanism should I choose to use?

Whether to use HTTP POST or HTTP Redirect for SSO and SLO is determined by the SAML bindings your SAML IdP supports. If your SAML provider supports multiple binding mechanisms then Citrix recommends you choose HTTP Post over HTTP Redirect as the SAML binding. There is no need to enable both SAML binding mechanisms on your SAML provider if it supports both. It is recommended you choose a single SAML binding type for both SSO and SLO.

SAML Binding Support

SAML Binding Supported by Citrix Cloud
HTTP POST Recommended.
HTTP Redirect Supported.
SAML Artifact binding Not Supported.
SOAP Not Supported.

Important:

HTTP Post is the recommended binding mechanism for both SSO and SLO requests for two reasons.

HTTP Post is easier to debug when signing enforcement is enabled on both sides of the SAML connections as the SAML XML contains easily identifiable sections that show the signature and certificate used. This is easier for humans to see and debug than if this signature data is embedded inside a very long Redirect URI which needs to be URL decoded.

HTTP Redirect URIs can grow very long and exceed a critical threshold which then leads to errors during SAML authentication and can cause login or logout failure. The GET binding type is limited to a maximum of 2,048 characters, minus the number of characters in the actual path. The POST method is not limited by the size of the URL for submitting name and value pairs.

Which SAML Binding Mechanism should I choose to use?