Client systems that use a smart card for user authentication must meet certain requirements.

VMware tested the following smart cards:

  • U.S. Department of Defense Common Access Card (CAC)

  • U.S. Federal Government Personal Identity Verification (PIV), also called FIPS-201

Each client system that uses a smart card for user authentication must have the following software and hardware:

  • Horizon Client

  • A compatible smart card reader

  • Product-specific application drivers

You must also install product-specific application drivers on the remote desktops or Microsoft 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.

Users who authenticate with smart cards must have a smart card and each smart card must contain a user certificate. 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 creating a server truststore file, see "Setting Up Smart Card Authentication" in the View Administration document.

In addition to meeting these requirements for Horizon Client systems, other View components must meet certain configuration requirements to support smart cards:

  • For information about configuring Connection Server to support smart card use, see "Setting Up Smart Card Authentication" in the View Administration document.

    Note:

    Smart cards are supported only with View 5.3.2 and later servers and desktops.

    You 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.

  • For information about tasks you might need to perform in Active Directory to implement smart card authentication, see "Setting Up Smart Card Authentication" in the View Administration document.

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 View 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 "Setting Up Smart Card Authentication" in the View Administration document.

If your environment uses an Access Point appliance rather than a security server for secure external access, you must configure the Access Point appliance to support the smart card user name hints feature. The smart card user name hints feature is supported only with Access Point 2.7.2 and later. For information about enabling the smart card user name hints feature in Access Point, see the Deploying and Configuring Access Point document.

Note:

Horizon Client still supports single-account smart card certificates when the smart card user name hints feature is enabled.