![]() ![]() True SSO Integration: Enable this setting on Connection Server to allow SSO to the desktop using True SSO.By default, channel bindings are enabled on the client. ![]() Disable Channel Bindings: An additional security layer to secure NTLM authentication.The NTLM group policy settings must be enabled in Horizon Client configuration. Allow NTLM Fallback: Uses NTLM authentication instead of Kerberos when there is no access to the domain controller.Horizon Client versions 2006 and 5.4 and earlier versions are considered older clients. Allow Legacy Clients: Support for older clients.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.Īccept logon as current user, you can enable the following user settings:.The session object resides in volatile memory and is not stored in Horizon LDAP or in a disk file. The session object is destroyed when the user logs out, the session times out, or authentication fails. The credentials are added when authentication occurs and are purged when the session object is destroyed. On the Connection Server instance, user credentials are encrypted and stored in the user session along with the username, domain, and optional UPN.To support this feature, user credentials are stored on both the Connection Server instance and on the client system. No further user authentication is required. With Horizon Client for Windows, when users select Log in as current user in the Options menu, the credentials that they provided when logging in to the client system are used to authenticate to the Horizon Connection Server instance and to the remote desktop using Kerberos. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |