Configuring Support for Citrix Federated Authentication Service

NOTE:

This documentation makes reference to ADFS as one example Identity Provider (IdP) that Imprivata customers can choose to leverage with Citrix FAS. However, it’s important to note that Citrix also supports other IdPs beyond ADFS, and those IDP’s are not detailed here in Imprivata’s documentation. For more information on IdPs, see your Citrix documentation.

As part of Citrix Federated Authentication Service (FAS), the Microsoft Active Directory Federated Services (ADFS) create a certificate on behalf of the user. Citrix FAS uses this certificate to log the user into their virtual desktops or applications, without requiring them to enter their Active Directory credentials.

Enabling Kerberos support allows Imprivata OneSign to trust the Citrix FAS user certificate, which extends the Citrix environment to Imprivata Virtual Desktop Access functionality.

  • Microsoft Active Directory Federated Services (ADFS) acts as the Identity Provider - during user authentication, the Imprivata agent requests a SAML artifact from the Imprivata appliance.

  • Citrix StoreFront functions as the Service Provider - The Imprivata agent uses the SAML artifact to authenticate the user to Citrix. Citrix StoreFront validates the SAML artifact with the Imprivata appliance.

Supported Workflows

Supported workflows include:

Citrix Web Portal — Manually Launched Desktops

Desired end-user workflow:

  1. The user opens a browser and accesses the Citrix web portal.

  2. The user supplies the credentials to access the Citrix web portal. All of the remote resources (VMs and apps) entitled to the user are displayed.

  3. The user selects the dedicated desktop to launch. The desktop launches and automatically logs the user in using the Imprivata OneSign agent installed on the desktop .

Citrix Web Portal — Manually Launched Applications

Desired end-user workflow:

  1. The user opens a browser and accessed the Citrix web portal.

  2. The user supplies the credentials to access the Citrix web portal. All of the remote resources (VMs and apps) entitled to the user are displayed.

  3. The user selects the applications to launch. If the application is a server-based desktop, the user is automatically logged into the Imprivata OneSign agent installed on the desktop.

Auto-Launched Desktops

Desired end-user workflow:

  1. Install the Imprivata agent on the endpoint computer.

  2. Enable Citrix dedicated desktop auto-launching by configuring a user policy and computer policy. Apply the computer policy to the endpoint and the user policy to the user.

  3. User logs onto the endpoint computer.

  4. The desktop is launched automatically. If the user has more than one desktop available, they select the appropriate desktop from the list.

Auto-Launched Applications

Desired end-user workflow:

  1. Install the Imprivata agent on the endpoint computer.

  2. Enable Citrix application auto-launching by configuring a user policy and computer policy. Apply the computer policy to the endpoint and the user policy to the user.

  1. User logs onto the endpoint computer.

    The selected Citrix applications are launched automatically. If the application is a Citrix full desktop, the user is logged into Imprivata OneSign on the full desktop automatically.

Before You Begin

Before you begin:

  • Review the Imprivata OneSign Supported Components to confirm that your Citrix environment meets the minimum requirements to support Citrix FAS with Imprivata OneSign.

  • Verify that the Citrix Federated Authentication Service (FAS) environment is functioning normally, independent of Imprivata OneSign, before installing and configuring Imprivata components.

    For more information, see your Citrix documentation on the FAS architecture and installation steps.

  • The following assumes that an Imprivata single-user agent (type 1) or an Imprivata agent for Citrix or Terminal servers (type 3) is installed on the computers that employees use to access their entitled resources. For complete details, see the Imprivata online help.

Configure Citrix StoreFront Authentication Methods

In Citrix StoreFront, configure the authentication methods for users accessing stores.

Configure Kerberos Authentication

Kerberos Prerequisites

Review the following prerequisites before you begin:

  • Verify that Kerberos is configured and enabled in your Windows environment. This topic details how to configure Imprivata OneSign for Kerberos authentication and assumes that the Kerberos deployment is running normally.

  • The Imprivata OneSign keytab utility (keytab utility), which you use to create and upload a keytab file to an appliance, uses ktpass to create and upload a keytab file to an appliance. The keytab utility is installed with the Imprivata agent.

    Ktpass is part of the Microsoft Windows Server resource kit. Beginning with Windows Server 2008, the resource kit tools are installed as part of the server role installation.

  • The endpoint computer from which you run the keytab utility and the primary appliance to which the Imprivata agent communicates must be in the same Active Directory domain.

    For example, if the fully qualified domain name (FQDN) of the endpoint computer is endpoint.example.com, then the Imprivata appliance FQDN could be server_name.example.com.

  • The Service Principal Name (SPN) of the appliance that the keytab utility registers with Active Directory is case-sensitive.

    The hostname and the domain name that appear in the Imprivata Appliance Console of this appliance must contain all lowercase letters.

  • If the Imprivata enterprise includes more than one domain that share a trust relationship, for example a parent company (company.com) and two subdomains (us.company.com and eu.company.com), make sure that at least one appliance is placed in company.com.

    Upload the keytab file to this appliance. Uploading to the appliance that is in the second-level domain (SLD) ensures that the keytab file is valid for all domains.

Enable Kerberos Authentication

Enabling Kerberos authentication requires that you:

Configure Imprivata OneSign