-
-
-
-
SAML Main IdP Chaining Support
-
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!
Directly Connecting the SAML Provider to Citrix Cloud VS IDP Chaining
Is IDP chaining supported for SAML login to Workspace or Citrix Cloud?
IDP chaining is supported provided the closest SAML IDP in the IDP chain is configured correctly and forwards SAML requests from Citrix Cloud onwards in the IDP chain, and the IDP chain returns the correct SAML response to Citrix Cloud.
Examples of IDP chains
- Citrix Cloud → F5 (directly connected to Citrix Cloud as the SAML provider) → Federated to Entra ID
- Citrix Cloud → Entra ID (directly connected to Citrix Cloud as the SAML provider) → Federated to ADFS
- Citrix Cloud → Entra ID (directly connected to Citrix Cloud as the SAML provider) → Federated to PingFederate
- Citrix Cloud → Entra ID (directly connected to Citrix Cloud as the SAML provider) → Federated to Okta
Can I get assistance and support from Citrix when debugging SAML issues if I am using an IDP chain?
Citrix support and Citrix Engineering can only debug SAML connections directly between Citrix Cloud and the closest SAML IDP in the chain.
Important:
Citrix is not responsible for debugging issues within a complex IDP chain upstream of the directly connected SAML provider.
Should I avoid IDP chaining if possible?
Citrix recommends directly connecting your SAML IDP to Citrix Cloud as this greatly reduces configuration and debugging complexity and minimises end user logon delays which can be introduced whilst Citrix Cloud waits for responses from the complex IDP chain. Many issues can arise with both SSO and SLO when multiple IDPs are chained together particularly when different SAML bindings are used by different IDPs within the IDP chain. A directly connected SAML provider will always be easier to debug and more performant than one that relies on upstream IDPs.
Share
Share
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.