-
-
-
-
SAML Main Metadata File Mode
-
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!
Create a SAML Connection using Metadata File Mode
How does Metadata File mode differ from Metadata URL mode?
On premise SAML IdPs such as an ADFS or PingFederate server may have restrictions that block public access to their SAML metadata URL endpoint, so using metadata URL mode is not possible. Citrix Cloud administrators can still benefit from automatic configuration of Citrix Cloud SAML connections if they are provided with a metadata.xml file exported from the SAML IdP. Citrix Cloud administrators can still upload this file within the SAML connection creation wizard.
How is Metadata File mode less useful than Metadata URL mode?
Metadata File mode is a static configuration stored inside Citrix Cloud. Citrix Cloud SAML connections that were created using metadata file mode cannot detect changes in the SAML application AFTER it has been uploaded into Citrix Cloud.
Metadata URL mode is a dynamic configuration obtained on demand. Metadata URL mode continuously polls your SAML IdP and can detect changes made inside the SAML application configuration immediately after they are made.
Configure the Citrix Cloud SAML connection using your IdP Metadata File
-
Download the metadata.xml file from the SAML application you wish to configure inside Citrix Cloud as a new SAML IdP connection.
-
Save the file to disk as
<filename>.xmland do not make any changes to its XML formatting or its contents. It is recommended you use completely unchanged and unformatted metadata.xml files taken directly from the SAML IdP after export.Important:
metadata.xml files are often signed by the IdP to prevent tampering. Any changes to the data inside the metadata.xml such as reformatting it using XML beautifying tools will invalidate the embedded signature and cause a failure to upload and parse the metadata.xml.
-
When you reach the Section 4 Service Provider section of the SAML wizard select Can’t use the metadata URL?.

-
Select Upload metadata file and drag and drop the metadata.xml file into the file upload dialogue or browse to the metadata.xml file on disk.
Here is an Okta example of a successfully imported metadata file.

-
Configure the SAML logout behaviour you want by either enabling or disabling SLO.
Refer to this in-depth article for Logout Considerations. -
Okta SAML connections ONLY. If the metadata file contains an SSO endpoint and a DNS domain string containing “okta” then Send NameID Policy as Unspecified for Okta will be automatically enabled. Okta SAML applications that use an Okta custom domain like mytenant.domain.com cannot be autodetected and Send NameID Policy as Unspecified for Okta must be manually enabled by the Citrix admin by clicking the check box.
-
Accept the default attribute mappings.
-
Configure your Citrix Cloud Admin Sign-In URL.
-
Examine the SAML wizard summary inside the Review section and verify the SAML configuration matches your expectations after parsing of the IdP metadata file.

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.