6.0.3

Table Of Contents
vSphere Authentication with vCenter
Single Sign-On 2
vCenter Single Sign-On is an authentication broker and security token exchange infrastructure. When a user
or a solution user can authenticate to vCenter Single Sign-On, that user receives SAML token. Going
forward, the user can use the SAML token to authenticate to vCenter services. The user can then perform the
actions that user has privileges for.
Because trac is encrypted for all communications, and because only authenticated users can perform the
actions that they have privileges for, your environment is secure.
Starting with vSphere 6.0, vCenter Single Sign-On is part of the Platform Services Controller. The
Platform Services Controller contains the shared services that support vCenter Server and vCenter Server
components. These services include vCenter Single Sign-On, VMware Certicate Authority, License Service,
and Lookup Service. See vSphere Installation and Setup for details on the Platform Services Controller.
For the initial handshake, users authenticate with a user name and password, and solution users
authenticate with a certicate. For information on replacing solution user certicates, see Chapter 3,
“vSphere Security Certicates,” on page 65.
After a user can authenticate with vCenter Single Sign-On, you can authorize the user to perform certain
tasks. In most cases, you assign vCenter Server privileges, but vSphere includes other permission models.
See “Understanding Authorization in vSphere,” on page 136.
N If you want to enable an Active Directory user to log in to a vCenter Server instance by using the
vSphere Client with SSPI, you must join the vCenter Server instance to the Active Directory domain. For
information about joining a vCenter Server Appliance with an external Platform Services Controller to an
Active Directory domain, see the VMware knowledge base article at hp://kb.vmware.com/kb/2118543.
This chapter includes the following topics:
n
“Understanding vCenter Single Sign-On,” on page 20
n
“Conguring vCenter Single Sign-On Identity Sources,” on page 29
n
“vCenter Server Two-Factor Authentication,” on page 36
n
“Using vCenter Single Sign-On as the Identity Provider for Another Service Provider,” on page 45
n
“Managing the Security Token Service (STS),” on page 47
n
“Managing vCenter Single Sign-On Policies,” on page 51
n
“Managing vCenter Single Sign-On Users and Groups,” on page 54
n
“vCenter Single Sign-On Security Best Practices,” on page 59
n
“Troubleshooting vCenter Single Sign-On,” on page 60
VMware, Inc.
19