Client systems that use a smart card for user authentication must meet certain requirements.
Client Hardware and Software Requirements
Each client system that uses a smart card for user authentication must have the following hardware and software:
- Horizon Client
- A compatible smart card reader
VMware tested the U.S. Department of Defense Common Access Card (CAC) and U.S. Federal Government Personal Identity Verification (PIV), also called FIPS-201 smart cards.
- Product-specific application drivers
Users who authenticate with smart cards must have a smart card and each smart card must contain a user certificate.
Remote Desktop and Application Software Requirements
A Horizon administrator must install product-specific application drivers on the remote desktops or RDS host. For Windows 7 remote desktops, the operating system installs the related driver when you insert a smart card reader and PIV card. For Windows XP and Windows Vista remote desktops, you can install the related driver by using ActivIdentify ActivClient.
Enabling the Username Hint Field in Horizon Client
In some environments, smart card users can use a single smart card certificate to authenticate to multiple user accounts. Users enter their user name in the Username hint field during smart card sign-in.
To make the Username hint field appear on the Horizon Client login dialog box, you must enable the smart card user name hints feature for the Connection Server instance in Horizon Administrator. The smart card user name hints feature is supported only with Horizon 7 version 7.0.2 and later servers and agents. For information about enabling the smart card user name hints feature, see the View Administration document.
If your environment uses an Unified Access Gateway appliance rather than a security server for secure external access, you must configure the Unified Access Gateway appliance to support the smart card user name hints feature. The smart card user name hints feature is supported only with Unified Access Gateway 2.7.2 and later. For information about enabling the smart card user name hints feature in Unified Access Gateway, see the Deploying and Configuring Unified Access Gateway document.
Additional Smart Card Authentication Requirements
In addition to meeting the smart card requirements for Horizon Client systems, other Horizon components must meet certain configuration requirements to support smart cards.
- Connection Server and security server hosts
An administrator must add all applicable Certificate Authority (CA) certificates for all trusted user certificates to a server truststore file on the Connection Server host or security server host. These certificates include root certificates and must include intermediate certificates if the user's smart card certificate was issued by an intermediate certificate authority.
When you generate a certificate for a blank PIV card, enter the path to the server truststore file on the Connection Server or security server host on the Crypto Provider tab in the PIV Data Generator tool.
For information about configuring Connection Server to support smart card use, see the View Administration document.
- Active Directory
- For information about tasks that an administrator might need to perform in Active Directory to implement smart card authentication, see the View Administration document.