View uses your existing Active Directory infrastructure for user and administrator authentication and management. For added security, you can integrate View with smart card authentication. You can also use two-factor authentication solutions, such as RSA SecurID and RADIUS, to authenticate remote desktop and application users.
Using Two-Factor Authentication You can configure a View Connection Server instance so that users are required to use RSA SecurID authentication or RADIUS (Remote Authentication Dial-In User Service) authentication.
Using Smart Card Authentication You can configure a View Connection Server instance or security server so that users and administrators can authenticate by using smart cards.
Using SAML Authentication for Workspace Integration The Security Assertion Markup Language (SAML) is an XML-based standard that is used to describe and exchange authentication and authorization information between different security domains. SAML passes information about users between identity providers and service providers in XML documents called SAML assertions.
Using Smart Card Certificate Revocation Checking You can prevent users who have revoked user certificates from authenticating with smart cards by configuring certificate revocation checking. Certificates are often revoked when a user leaves an organization, loses a smart card, or moves from one department to another.
Using the Log In as Current User Feature Available with Windows-Based Horizon Client With Horizon Client for Windows, when users select the Log in as current user check box, the credentials that they provided when logging in to the client system are used to authenticate to the View Connection Server instance and to the remote desktop. No further user authentication is required.
Allow Users to Save Credentials Administrators can configure View Connection Server to allow Horizon Client mobile devices to remember a user's user name, password, and domain information. If users choose to have their credentials saved, the credentials are added to the login fields in Horizon Client on subsequent connections.