-
-
-
-
SAML Main Choosing Binding Mechanism
-
SAML using Entra ID for Guest and B2B identities for workspace authentication
-
This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
此内容已经过机器动态翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
この記事は機械翻訳されています.免責事項
이 기사는 기계 번역되었습니다.책임 부인
Este artigo foi traduzido automaticamente.(Aviso legal)
这篇文章已经过机器翻译.放弃
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Translation failed!
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.
Share
Share
In this article
This Preview product documentation is Citrix Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Citrix Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Citrix product purchase decisions.
If you do not agree, select I DO NOT AGREE to exit.