Administration

Table Of Contents
To support this feature, user credentials are stored on both the Connection Server instance and on
the client system.
n On the Connection Server instance, user credentials are encrypted and stored in the user
session along with the username, domain, and optional UPN. The credentials are added when
authentication occurs and are purged when the session object is destroyed. The session object
is destroyed when the user logs out, the session times out, or authentication fails. The session
object resides in volatile memory and is not stored in Horizon LDAP or in a disk file.
n On the Connection Server instance, enable the Accept logon as current user setting to allow
the Connection Server instance to accept the user identity and credential information that is
passed when users select Log in as current user in the Options menu in Horizon Client.
Important You must understand the security risks before enabling this setting. See, "Security-
Related Server Settings for User Authentication" in the
Horizon 7 Security
document.
n On the client system, user credentials are encrypted and stored in a table in the Authentication
Package, which is a component of Horizon Client. The credentials are added to the table when
the user logs in and are removed from the table when the user logs out. The table resides in
volatile memory.
When you select Accept logon as current user, you can enable the following user settings:
n Allow Legacy Clients: Support for older clients. Horizon Client versions 2006 and 5.4 and
earlier versions are considered older clients.
n Allow NTLM Fallback: Uses NTLM authentication instead of Kerberos when there is no access
to the domain controller. The NTLM group policy settings must be enabled in Horizon Client
configuration.
n Disable Channel Bindings: An additional security layer to secure NTLM authentication. By
default, channel bindings are enabled on the client.
Note If channel binding is enabled, confirm that NTLMv2 is turned on using the
LMCompatibilityLevel switch and that the security level 3 or higher in the user environment.
For more information, see the Microsoft documentation here.
n True SSO Integration: Enable this setting on Connection Server to allow SSO to the desktop
using True SSO. For example, in a nested mode, True SSO is used to log on to a nested client
and then a secondatry desktop logon was performed. For information on nested mode, see
the
VMware Horizon Client for Windows Installation and Setup Guide
.
n Disabled: The user has to enter login information if the client did not receive logon
credentials.
n Optional: Client credentials will be used, if available, else True SSO will be used. This is the
recommended setting if both True SSO and Log in as current user are enabled.
n Enabled: True SSO will be used to log on to the desktop.
Horizon 7 Administration
VMware, Inc. 92