Citrix Cloud

Configure an On-Premise PingFederate Server as the SAML Provider for Workspaces and Citrix Cloud

This article was written by collaboration between both Citrix and Ping engineers and has been reviewed by both parties to ensure technical accuracy at the time of writing. Refer to Ping documentation for instructions on how to provision, configure and licence an on premise PingFederate server for use as a SAML provider as this is beyond the scope of this article.

This document was written using PingFederate versions 11.3 and 12.


This article specifically addresses SAML configuration and ensure that the following conditions are fulfilled.

  • You have already provisioned an on-premise PingFederate server within your organization and obtained the necessary license. For more information, see PingFederate Installation.
  • You need to have installed a supported version of Java on to the PingFederate server. Refer to Ping Identity documentation for the supported Java versions. For more information, see Java PingFederate Requirement.
  • You have configured the required networking and firewall rules to allow Citrix Cloud and Workspace to redirect to the on premise PingFederate server during the Workspace/Citrix Cloud admin console SAML logon process. For more information, see PingFederate Network Requirements.
  • You have imported a publicly signed x509 certificate onto your PingFederate server that can act as server certificate for the PingFederate server.
  • You have imported a publicly signed x509 certificate onto your PingFederate server that can act as a SAML signing certificate for the IdP. This certificate must be uploaded to Citrix Cloud during the SAML connection process.
  • You have connected your on-premise Active Directory to PingFederate. For more information, see PingFederate LDAP Datastore


While configuring PingFederate for use with Citrix Cloud and Workspace, refer to PingFederate documentation to understand what individual SAML settings do and to help supplement the instructions provided here.

Configure an Active Directory Connection to your AD domain using a DataStore within PingFederate

  1. Configure an Active Directory connection within Data Stores.

    Configure Active Directory connection

  2. Select Type as Directory (LDAP).

    Select Directory

  3. Configure your domain controllers for LDAPS connections and add your list of domain controller FQDNs within the hostnames field. Then click Test Connection.

    Configure domain controllers

  4. Once configured, the Active Directory Connection should resemble the following example:

    Active Directory connection

Upload the Citrix Cloud SAML Signing Certificate

  1. Click the Security tab
  2. Upload the SAML signing certificate you wish PingFederate to use within Signing & Decryption Keys and Certificates.

    Signing and decryption keys and certificates


    The certificate used is a publicly signed Digicert certificate in this example.

  3. Upload any CA certificates used to sign your PingFederate server SAML signing certificate.

    SAML signing certificate


The PingFederate server certificate and SAML signing certificate can be the same SSL cert or you can use different SSL certs. You need to provide a copy of the SAML signing certificate to Citrix Cloud when you configure the SAML connection.

SSL Server certificates

Upload the Citrix Cloud Metadata

  1. Provide a name for the Citrix Cloud metadata and enter the metadata URL corresponding to the Citrix Cloud region where your Citrix Cloud tenant is located.

    Partner Medata URL

  2. Once configured, the Citrix Cloud metadata configuration should resemble the following example.

    Partner Metada URL configured

Configure a password credential validator within PingFederate

For more information, see PingFederate Password Credential validator

  1. Configure the password credential validator type as LDAP username and password.

    Password credential validators

  2. Configure the Instance Configuration. Select the AD domain connection and data store that you configured earlier Configure an Active Directory Connection to your AD domain using a DataStore within PingFederate. Enter a suitable LDAP filter as shown in the example. (((sAMAccountName=${username})(userPrincipalName=${username}))

    Configure instance configuration

    Note: The example filter matches both sAMAccountName and userPrincipalName AD username formats, enabling the end users to sign in to Workspace or Citrix Cloud with either of these. The example filter accommodates both sAMAccountName and userPrincipalName AD username formats, enabling end users to sign in to Workspace or Citrix Cloud using either of these formats.

  3. Configure the Extended Contract.

    Extended contract

  4. The Password Credential Validator summary should resemble this example.

    Password credential validator

Configure the IDP Adapter within PingFederate

For more information, see PingFederate HTML form adapter

  1. Create a new IDP adapter of type HTML Form IdP Adapter.

    Create adapter instance

  2. Select the existing Password Credential Validator you configured earlier and configure the IDP Adapter. For more information, see Configure a password credential validator within PingFederate.

    Password credential validator

  3. Configure the Extended Contract with SAML attributes that are passed to Citrix Cloud or Workspaces during SAML logon.

    Configure extended contract

  4. Configure the Adapter Attributes.

    Configure adapter attributes

  5. Configure the Adapter Contract Mapping where SAML attributes are mapped to LDAP user attributes from AD identities. Click Configure the adapter contract.
  6. Configure Attribute Sources & User Lookup.

    Attribute Sources and User Lookup

  7. Configure Adapter Contract Fulfilment. Select LDAP and the name of your active directory data store as the source of the user attribute data. Value is the active directory attribute for the user such as objectGUID or objectSid.

    Configure Adapter Contract Fulfilment

Configuring the Service Provider Connection (SAML application) for Citrix Cloud or Workspaces

The sample PingFederate configuration provided below assumes the following SAML authentication requirements within your organisation.

  • SAML authentication requests sent from Workspace/Citrix Cloud admin console MUST be signed.
  • SAML HTTP POST bindings will be used for both SSO and SLO requests.
  • Single Logout (SLO) is a requirement within your organisation. When an end user signs out of Workspace or the Citrix Cloud admin console, a SAML SLO request is sent from Citrix Cloud to the SAML provider (IdP) to sign out the user.
  • PingFederate requires signed HTTP POST requests to initiate sign out. SAML provider requires Signed SLO requests.

    SLO Binding Mechanism

For more information, see PingFederate SP Management


  1. Configure the Connection Template.

    Configure the Connection Template

  2. Configure the Connection Type and select Browser SSO profiles and SAML 2.0.

    Configure Connection Type

  3. Configure the Connection Options.

    Configure connection options

  4. Import the Citrix Cloud Metadata. Select URL and the CitrixCloudProdMetadata URL you created earlier and click Load Metadata

    Import Citrix Cloud Metadata

  5. Configure General Info. Set the Service Provider Connection Entity ID, Base URL and Connection Name to the Citrix Cloud SAML endpoint for your Citrix Cloud customer region.

    Configure General Info

  6. Configure Protocol Settings.

    Configure Protocol settings

  7. Use the default Assertion Lifetime settings.

    Assertion lifetime settings

  8. Configure SAML Assertion Creation.
    1. Click Configure Assertion Creation

      Configure Assertion Creation

    2. Select Standard.

      Select Standard

  9. Configure Attribute Contract.

    Configure Attribute Contract

  10. Configure Adapter Instance.

    Configure Adapter Instance

  11. Configure Mapping Method.

    Configure Mapping Method

  12. Configure Attribute Contract Fulfilment.

    Configure Attribute Contract Fulfilment

  13. Configure Issuance Criteria as the defaults with no conditions.

    Configure Issuance Criteria

  14. The completed IDP Adapter Mapping appears as follows:

    completed IDP Adapter Mapping

  15. Configure Protocol Settings. SAML paths required by Citrix Cloud will be appended to your PingFederate server base URL. It is possible to override the base URL by entering a full path within the endpoint URL field but this is usually unnecessary and undesirable. Base URL -
    1. Configure the Assertion Consumer Service URL which appends the SAML path to the PingFederate server base URL. EndpointURL - /saml/acs

      Configure the Assertion Consumer Service URL

    2. Configure SLO Service URL. EndpointURL - /saml/logout/callback

      Configure SLO Service URL


    The Citrix Cloud SAML connection requires a PingFederate Logout URL to be configured to match this if you wish to perform SLO when signing out of Workspace or Citrix Cloud. Failing to configure the Logout URL within your SAML connection will cause end users to just sign out of Workspace but not PingFederate.

    1. Configure Allowable SAML Bindings.

      Configure Allowable SAML Bindings

    2. Configure Signature Policy.

      Configure Signature Policy


    SAML signing settings must be configured consistently on both sides of the SAML connection. Workspace or Citrix Cloud (SP) must be configured to send signed SSO and SLO requests.

    1. PingFederate (IDP) must be configured to perform enforcement of signed requests using the Citrix Cloud SAML signing verification certificate.

      Enforcement of signed requests

    2. Configure the Encryption Policy.

      Configure the Encryption Policy


      It is recommended to set Encryption to NONE during initial setup and testing so you can debug any issues with missing or incorrect SAML attributes in the assertion. If you require encrypted assertions, it is recommended that you enable encryption after proving that the logon to Workspace or Citrix Cloud is successful and all resources have been successfully enumerated and can be launched. Debugging issues with SAML whilst encryption is enabled will be impossible if you cannot view the plaintext contents of the SAML assertion.

    3. Review the Summary tab.

      Summary tab

    4. Review the Citrix Cloud Service Provider (SP) Connection. Once the Citrix Cloud SP connection is configured it should look like this example:

      Summary Summary Summary Summary

      Userful tip:

      Use the SP Connection Activation and Summary page to review your SAML application and for debugging purposes as it allows quick and easy configuration changes to be made. The SP Connection Activation and Summary page allows you to navigate to any of the SAML configuration sub sections by clicking on the title of that section. Click on any of the titles highlighted in red to update these settings.

    Protocol Settings

  16. The completed Citrix Cloud SP connection should appear in the list like this.

    Citrix Cloud SP connection

  17. It is possible to export the SP connection in the form of an XML file. Citrix recommends taking a backup of your SP connection once you have tested it with Citrix Cloud and Workspace.

    Export the SP connection