Adding a vCenter server Single Sign-On Active Directory Identity Source Using LDAPS fails when using an External LDAP Load Balancer
book
Article ID: 380859
calendar_today
Updated On:
Products
VMware vCenter Server
Issue/Introduction
Cannot add a vCenter Single Sign On (SSO) Active Directory Identity Source using LDAPS using an external load balancer for ldaps
Environment
VMware vCenter Server
Cause
This issue arises when the Active Directory Domain Controllers are configured behind an external load balancer for LDAPS connections.
When vCenter attempts to connect to ldaps://ldap.example.com:636, the load balancer redirects the traffic to one of the servers in the pool.
Additionally, a certificate that establishes trust for the LDAPS endpoint of the Active Directory server is required when using ldaps:// in either the primary or secondary LDAP URL.
Resolution
Export the LDAP server certificates for all domain controllers behind the load balancer using OpenSSL command
Identify the list of domain controllers under the load balancer for LDAPS.
Connect to the vCenter Server Appliance with SSH and login as root.
Run the following command to show the LDAP certificate: openssl s_client -connect dc1.domain.com:636 -showcerts
The full contents of the SSL certificate will be displayed. The certificate chain appears similar to:
The top most certificate in this chain is the certificate of the domain controller.
Copy the complete string including -----BEGIN CERTIFICATE----- until (including) -----END CERTIFICATE----- into a text file.
Remove any additional characters after -----END CERTIFICATE-----.
Save that file as .cer.
Example: If you have 6 domain controllers under the load balancer, repeat the command for each DC openssl s_client -connect dc2.domain.com:636 -showcerts openssl s_client -connect dc3.domain.com:636 -showcert