6.1

Table Of Contents
n
In the locked.properties file on the View Connection Server or security server host, verify that the
useCertAuth property is set to true and is spelled correctly.
The locked.properties file is located in install_directory\VMware\VMware
View\Server\sslgateway\conf. The useCertAuth property is commonly misspelled as userCertAuth.
n
If you configured smart card authentication on a View Connection Server instance, check the smart card
authentication setting in View Administrator.
a Select View Configuration > Servers.
b On the Connection Servers tab, select the View Connection Server instance and click Edit.
c If you configured smart card authentication for users, on the Authentication tab, verify that Smart
card authentication for users is set to either Optional or Required.
d If you configured smart card authentication for administrators, on the Authentication tab, verify
that Smart card authentication for administrators is set to either Optional or Required.
You must restart the View Connection Server service for changes to smart card settings to take effect.
n
If the domain a smart card user resides in is different from the domain your root certificate was issued
from, verify that the user’s UPN is set to the SAN contained in the root certificate of the trusted CA.
a Find the SAN contained in the root certificate of the trusted CA by viewing the certificate
properties.
b On your Active Directory server, select Start > Administrative Tools > Active Directory Users and
Computers.
c Right-click the user in the Users folder and select Properties.
The UPN appears in the User logon name text boxes on the Account tab.
n
If smart card users use the PCoIP protocol to connect to single-session desktops, verify that the View
Agent PCoIP Smartcard feature is installed on the single-user machines. The PCoIP Smartcard feature
lets users log in to single-session desktops with smart cards using the PCoIP protocol. RDS hosts, which
have the Remote Desktop Services role installed, support the PCoIP Smartcard feature automatically
and you do not need to install the feature.
n
Check the log files in drive:\Documents and Settings\All Users\Application Data\VMware\VDM\logs
on the View Connection Server or security server host for messages stating that smart card
authentication is enabled.
Using SAML Authentication for Workspace Portal 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.
The Workspace Portal and View integration implementation uses the SAML 2.0 standard to establish
mutual trust, which is essential for single sign-on (SSO) functionality. When SSO is enabled, users who log
in to Workspace Portal with Active Directory credentials can launch remote desktops and applications
without having to go through a second login procedure.
When Workspace Portal and View are integrated, Workspace Portal Manager generates a unique SAML
artifact whenever a user logs in to Workspace Portal and clicks a desktop or application icon.
Workspace Portal Manager uses this SAML artifact to create a Universal Resource Identifier (URI). The URI
contains information about the View Connection Server instance where the desktop or application pool
resides, which desktop or application to launch, and the SAML artifact.
Chapter 3 Setting Up Authentication
VMware, Inc. 51