Administration

Table Of Contents
If users choose to save their credentials, the credentials are added to the login elds in Horizon Client on
subsequent connections.
To enable this feature, you must set a value in View LDAP to indicate how long to save credential
information in the client. For Horizon Client for Mac, this feature is supported only in version 4.1 or later.
N On Windows-based Horizon clients, the feature for logging in as the current user avoids requiring
users to supply credentials multiple times.
Configure a Timeout Limit to Save Horizon Client Credentials
You congure a timeout limit that indicates how long to save Horizon Client credential information on
mobile devices and Mac client systems by seing a value in View LDAP. The timeout limit is set in minutes.
When you change View LDAP on a View Connection Server instance, the change is propagated to all
replicated View Connection Server instances.
Prerequisites
See the Microsoft TechNet Web site for information on how to use the ADSI Edit utility on your Windows
operating system version.
Procedure
1 Start the ADSI Edit utility on your View Connection Server host.
2 In the Connection Seings dialog box, select or connect to DC=vdi,DC=vmware,DC=int.
3 In the Computer pane, select or type localhost:389 or the fully qualied domain name (FQDN) of the
View Connection Server host followed by port 389.
For example: localhost:389 or mycomputer.mydomain.com:389
4 On the object CN=Common, OU=Global, OU=Properties, edit the clientCredentialCacheTimeout
aribute value.
When clientCredentialCacheTimeout is not set or is set to 0, the feature is disabled. To enable this
feature, you can set the number of minutes to retain the credential information, or set a value of -1,
meaning that there is no timeout.
On View Connection Server, the new seing takes eect immediately. You do not need to restart the View
Connection Server service or the client computer.
Setting Up True SSO
With the True SSO (single sign-on) feature, after users log in to VMware Identity Manager using a smart
card or RSA SecurID or RADIUS authentication, users are not required to also enter Active Directory
credentials in order to use a remote desktop or application.
If a user authenticates by using Active Directory credentials, the True SSO feature is not necessary, but you
can congure True SSO to be used even in this case, so that the AD credentials that the user provides are
ignored and True SSO is used.
When connecting to a virtual desktop or remote application, users can select to use either the native Horizon
Client or HTML Access.
This feature has the following limitations:
n
This feature does not work for virtual desktops that are provided by using the View Agent Direct
Connection plug-in.
n
This feature is supported only in IPv4 environments.
Chapter 5 Authenticating Users Without Requiring Credentials
VMware, Inc. 75