Configuring Persistent Applications for Citrix XenApp with Manually Launched Applications

This topic includes information about configuring Imprivata support for persistent applications in Citrix XenApp® published desktops.

The persistent applications feature enables published applications to remain running as a generic Windows user account or anonymously. It allows a user to launch their application with a generic user account but still allows the user to launch other applications as a named user.

  • A persistent application is automatically launched using generic user credentials when the endpoint computer starts.

  • The user can have an additional Citrix session authenticated under their own explicit credentials, in addition to the persistent app which is launched under generic credentials.

  • When a user closes a persistent application, it remains closed until the endpoint computer locks.

  • When the endpoint computer locks, the persistent application is automatically launched again so it is ready for the next user.

  • If the user closes the persistent application, it is automatically launched again when the endpoint computer is locked.

Supported Two-Factor Authentication Methods

The following two-factor authentication methods are supported when authenticating to the endpoint computer. The methods are listed as first factor plus second factor.

  • Fingerprint plus network password or PIN

  • Passive proximity card plus network password, PIN, or fingerprint

For a proximity card first factor, you can allow a limited user choice for the second factor, for example, network password or fingerprint.

For more information on authentication methods, see Enterprise Access Management SSO Authentication Methods.

Before You Begin

Review the Expected User Workflow

The following illustrates the expected workflow when the Enterprise Access Management environment is configured for persistent applications.

In this workflow example, User A and User B are Imprivata Virtual Desktop Access users. User C is not part of the Imprivata Virtual Desktop Access policy.

  1. A Windows only endpoint starts and Enterprise Access Management starts a generic user session for the configured application.

  2. User A authenticates. The application session is still running as the generic user or anonymous account throughout User A's session.

  3. If profiled for Single Sign-On, for example Epic, Enterprise Access Management proxies the user credentials and the user is logged into the persistent application.

  4. Imprivata Virtual Desktop Access logs User A into Citrix Workspace app. All entitled user applications are delivered to the endpoint.

  5. The endpoint is locked due to inactivity or User A taps to lock the endpoint.

  6. User B authenticates. Imprivata Virtual Desktop Access detects the user switch and logs the user out of the persistent application.

    The Citrix session of User A is disconnected. The persistent application session continues to run as the generic user or anonymous account throughout the session of User B.

  7. User B works with the persistent application, closes it and then locks the workstation.

  8. Imprivata Virtual Desktop Access relaunches the persistent application.

  9. User C authenticates. Because User C is not part of the Imprivata Virtual Desktop Access policy, the persistent application closes.

Installation Sequence