Connecting to Omnissa Horizon Hosts Using Proximity Cards

If Imprivata OneSign has been set up for your deployment, you can connect to Omnissa Horizon Hosts using proximity cards.

Imprivata OneSign enables users to access corporate networks, desktops, and applications with a single sign on. This reduces the need for maintaining separate passwords and prevents unauthorized access.

While Imprivata OneSign supports a range of authentication options, at present, only proximity cards are supported.

This topic describes how to add a connection and use proximity cards to access Omnissa Horizon Hosts.

!!! info Note: Support for Failover Gateways The supports failover Security Gateways in a Connection Manager and Security Gateway deployment. If the primary gateway used to establish a PCoIP session fails unexpectedly, the session is automatically transferred to the next available gateway.

Session failover is only available if failover gateways are configured on the machines where the Connection Manager and/or Security Gateway are installed. No additional configuration is required on the HP Anyware Clients.

Instructions for configuring failover gateways is available in the topic "Configuring Failover Security Gateways" of the Connection Manager and Security Gateway Administrators' Guide.

Adding a Connection

Following are the steps users should follow to add a connection:

1. Launch the Trusted Zero Client.

2. To add connection, select the options in the Anyware add connection page:

   1. Select the required connection type from the dropdown.
   2. Enter the OneSign server address.
   3. Provide a connection name (optional).

3. After providing the details, users are presented with a list of connections to select from.

   Note: Authenticating Connection Using Proximity Cards

   Upon selection of the connection, users are directed to the smart card verification page.

Authenticating a Connection Using Proximity Cards

1. For autheticating the connection using proximity cards, users need to tap their proximity card on the card reader to continue the authetication process.

2. Users must wait while the proximity card authentication is being processed.

3. Here are a series of conditions that a user may encounter after the authentication process:

   1. Smart card verification is successful:

      • Users are directed to a Smart Card Verification page, where they need to enter the PIN.

        • Upon entering the PIN correctly, the user is successfully logged in and can select from the avilable list of desktop names.

        • When a PIN is entered incorrectly, users receive a warning notification along with the number of attempts remaining.

   2. Card reader is unable to read the card:

      • Users need to try tapping the card again or use another card.

   3. Card verification failed (unable to validate card certificate(s)):

      • A notification appears notifying users to try another card.

   4. Card verification failed (unable to verify card, untrusted certificate):

      • A notification appears notifying users to try another card.

   5. Card is blocked:

      • User needs to contact sytem admin for support or need to try another card.