During the installation of vCenter Single Sign On (SSO), the installer will attempt to detect the Active Directory (AD) domain for the logged in user and add it as an Identity Source. For the most part, this works fine; however, I’ve run into a couple of instances so far deploying vSphere 5.1 to customers where they either want to add a second AD Identity Source or for one reason or another (running the installer as the local administrator is a typical case), the installer didn’t properly add a non-System-Domain Identity Source.
1. Log in to the vCenter Server Web Client as admin@system-domain (password defined during SSO installation).
2. Click Administration in the left-hand pane.
3. Under Sign-On and Discovery, click Configuration. On the Identity Sources tab, click the green + icon to add a new Identity Source.
4. Choose Active Directory as the Identity Source type, then fill in the Identity Source Settings information for your Active Directory domain
a. Name - Name of the identity source, e.g., domain name
b. Primary Server URL - Primary domain controller
c. Secondary Server URL - Secondary domain controller (optional)
d. Base DN for Users - The base domain name for users (optional)
e. Domain Name - The domain’s DNS name, e.g., domain.tld
f. Domain Alias - The domain’s NetBIOS name, e.g. DOMAIN (optional)
g. Base DN for Groups - The base domain name for groups (optional)
h. Authentication Type - Choose Password
i. User Name - A domain user with minimum read-only rights to the base DN for users and groups
j. Password - The password for the above user
5. Click Test Connection to make sure you have connectivity.
6. Click OK to add the Identity Source.
7. Select the new Active Directory Identity Source, then click the icon for Add to Default Domains. Click OK on the subsequent warning.
8. Click the up arrow to move your Active Directory domain to the top, then click the Save button to save the configuration
You’ve now added a new Active Directory Identity Source.