Impact of 2020 LDAP Channel Binding and LDAP Signing requirement for Microsoft Windows in vCenter Server
search cancel

Impact of 2020 LDAP Channel Binding and LDAP Signing requirement for Microsoft Windows in vCenter Server

book

Article ID: 309018

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

Microsoft had released a security update on Windows Update to enable LDAP channel binding and LDAP signing hardening changes. The purpose of this security update is to harden security against man-in-middle attacks by requiring ldap binds to be signed. To avoid any system environment compatibility issues, Microsoft strongly advise administrators to enable LDAP channel binding and LDAP signing between now and mid-January 2020 to find and fix any operating systems, applications or intermediate device compatibility issues in their environment.  If any compatibility issue is found, administrators will need to contact the manufacturer of that particular OS, application or device for support.

To learn more, please refer to: https://support.microsoft.com/en-us/help/4520412/2020-ldap-channel-binding-and-ldap-signing-requirement-for-windows

vCenter server with AD over LDAP fail to login users with message "Strong(er) authentication required"

Configuring AD over LDAP fails with Error ""Failed to probe provider connectivity [URI: ldap://vCenter/PSC FQDN:389 ]; tenantName [vsphere.local], userName [CN=Administrator,CN=Users,DC=SSODOMAIN,DC=com] Caused by: Strong(er) authentication required"



Environment

VMware vCenter Server Appliance 6.5.x
VMware vCenter Server Appliance 6.7.x
VMware vCenter Server 7.x
VMware vCenter Server 8.x

Resolution

vCenter server identity source can be configured as AD over LDAP,  AD over LDAPs or vCenter Server supports federated authentication.
 
Refer to vSphere Authentication documentation.

Additional Information