Users can log in to vCenter Server only if they are in a domain that has been added as a vCenter Single Sign-On identity source. vCenter Single Sign-On administrator users can add identity sources, or change the settings for identity sources that they added.
An identity source can be a native Active Directory (Integrated Windows Authentication) domain or an OpenLDAP directory service. For backward compatibility, Active Directory as an LDAP Server is also available. See Identity Sources for vCenter Server with vCenter Single Sign-On.
- localos
- All local operating system users. If you are upgrading, those localos users who can already authenticate can continue to authenticate. Using the localos identity source does not make sense in environments that use an embedded Platform Services Controller.
- vsphere.local
- Contains the vCenter Single Sign-On internal users.
Prerequisites
If you are adding an Active Directory identity source, the vCenter Server Appliance or the vCenter Server Windows machine must be in the Active Directory domain. See Add a Platform Services Controller Appliance to an Active Directory Domain.
Procedure
What to do next
When an identity source is added, all users can be authenticated but have the No access role. A user with vCenter Server Modify.permissions privileges can give users or groups of users privileges. The privileges enable the users or groups to log in to vCenter Server and to view and manage objects. You can configure permissions so that users and groups from a joined Active Directory domain can access the vCenter Server components. See the vSphere Security documentation.