LDAP connection test fails after integrating Windows Server 2025 as Active Directory with VMware Cloud Director

search cancel

book

calendar_today

VMware Cloud Director

After configuring Windows Server 2025 as Active Directory (AD) and set it as LDAP server in VMware Cloud Director (VCD), LDAP connection test failed.

You may see the similar following log at vcloud-container-info.log and vcloud-container-debug.log in VCD.

The server requires binds to turn on integrity checking if SSL\TLS are not already active on the connection

VMware Cloud Director 10.6.x

In Windows Server 2025, LDAP signing is required by default, and connection without LDAP signing is rejected.

Follow either of the following action:

Disable LDAP signing in AD.
- Configure AD to allow the unsigned LDAP connection.
  Ref: How to enable LDAP signing in Windows Server
  - For details, please contact the OS vendor that provides AD.
Use LDAPS connection in VCD.
- Configure the VCD's LDAP settings to use LDAPS.
  Ref: Edit, Test, and Synchronize an LDAP Connection Using Your
  - The default port for LDAPS is 636.
  - Require checking "Use SSL".

If you have not installed the AD root CA certificate on the VCD, refer to the following KB to install it.
Ref: Install the Certification Authority on Windows Server

thumb_up Yes

thumb_down No