Administration

Table Of Contents
5 Click OK.
6 Restart the View Connection Server service.
You must restart the View Connection Server service for changes to smart card settings to take effect,
with one exception. You can change smart card authentication settings between Optional and
Required without having to restart the View Connection Server service.
Currently logged in user and administrators are not affected by changes to smart card settings.
What to do next
Prepare Active Directory for smart card authentication, if required. See Prepare Active Directory for Smart
Card Authentication.
Verify your smart card authentication configuration. See Verify Your Smart Card Authentication
Configuration.
Configure Smart Card Authentication on Third-Party
Solutions
Third-party solutions such as load balancers and gateways can perform smart card authentication by
passing a SAML assertion that contains the smart card's X.590 certificate and encrypted PIN.
This topic outlines the tasks involved in setting up third-party solutions to provide the relevant X.590
certificate to View Connection Server after the certificate has been validated by the partner device.
Because this feature uses SAML authentication, one of the tasks is to create a SAML authenticator in
View Administrator.
For information about configuring smart card authentication on Unified Access Gateway, see Deploying
and Configuring Unified Access Gateway.
Procedure
1 Create a SAML authenticator for the third-party gateway or load balancer.
See Configure a SAML Authenticator in Horizon Administrator.
2 Extend the expiration period of the View Connection Server metadata so that remote sessions are not
terminated after only 24 hours.
See Change the Expiration Period for Service Provider Metadata on Connection Server.
3 If necessary, configure the third-party device to use service provider metadata from View Connection
Server.
See the product documentation for the third-party device.
4 Configure smart card settings on the third-party device.
See the product documentation for the third-party device.
View Administration
VMware, Inc. 55