Configuring a vCenter Single Sign-On Identity Source using LDAP with SSL (LDAPS)
book
Article ID: 316596
calendar_today
Updated On:
Products
VMware vCenter Server
Issue/Introduction
This article provides steps to configure an Identity Source in vCenter Single Sign-On (SSO) to use a secured LDAP over SSL (LDAPS) connection. This is appropriate in secure environments to encrypt all LDAP traffic in between vCenter Server and the authorizing Identity Source.
Caution: This article provides a general how-to guide. Consult with the Directory Administrators in your organization for specific procedures.
For information on configuring the LDAP server to use SSL, see the Microsoft article LDAP over SSL (LDAPS) Certificate . The steps in this article assume that the Domain Controller in question has a valid certificate available and that this certificate has been exported. See the Microsoft article linked above for more details.
To configure an Identity Source in vCenter Single Sign On to use a secured LDAPS:
If this is an ELM (Enhanced Linked Mode) environment, please only perform the following steps on a single vCenter, as the IdP configurations will replicate to the other linked vCenter servers.
Take appropriate snapshot of VCSA VM. Note: If ELM, please make sure to take offline snapshots of all linked VCSA VMs before proceeding.
Log in to the vSphere Web Client using an Single Sign On Administrator.
Under Menu, select Administration > Configuration > Identity Sources
Remove the existing Identity source
Click Add and select Active Directory over LDAP to configure a new source
Enter the required information in the Add Identity Source wizard (Active Directory over LDAP)
Ensure that you add specific LDAPs url(s).
Click on Browse next to "Certificates (For LDAPS)" and select the certificates that were exported from the domain controllers specified in the LDAPs URL(s). Refer to LDAP over SSL (LDAPS) Certificate for more details.
Click on Add and the new source will be listed in the client
Additional Information
Important Information about configuring an LDAPS identity source
If an existing identity source exists with the same domain, that identity source will have to be removed before configuring an LDAPS identity source.
If you are updating or replacing the SSL certificate the identity source will need to be removed & re-added.
If the "Username" used during adding Identity Source gets locked/disabled/password expired; then the AD user login's to vCenter would fail. You have to redo the task and update the AD username and password again.
Ensure the account being used to add the identity source is not in a restricted AD group, such as the Protected Users group .
vSphere includes an openssl binary located at C:\Program Files\VMware\Infrastructure\Inventory Service\bin\openssl.
Run the command to gather the SSL certificate information from any Domain Controller desired: