Error : 'Failed to connect to Active Directory, please check the configuration and try again' when configuring VCF SSO
search cancel

Error : 'Failed to connect to Active Directory, please check the configuration and try again' when configuring VCF SSO

book

Article ID: 438392

calendar_today

Updated On:

Products

VCF Operations VMware vSphere ESXi

Issue/Introduction

  • When configuring VCF Single Sign-On (SSO) using the Identity Broker appliance in a VMware Cloud Foundation (VCF) 9.x environment, saving the configuration fails with the below error:

    Saving configuration settings failed with the following error:
     Failed to connect to Active Directory, please check the configuration and try again




  • Basic network tests confirm that port 389 is open and communication with the AD/LDAP server is established.

  • The following error is observed in the vidb-external/console-log-##.log file on the identity appliance: 

    Unable to establish a connection to Active Directory or perform a bind operation, please check the configuration and try again
    ...
    Request failed with status_code: 400 with exception com.vmware.vidm.common.vertx.exceptions.WebApplicationException, cause: com.vmware.vidm.usergroup.model.exceptions.broker.connector.LdapDirectoryCommunicationFailureException
  • The error 'Strong(er) authentication required (8)' is observed when using ldapsearch to test the connection to the AD/LDAP server.

    #ldapsearch -H ldap://<AD_HOST_IP> -D "CN=<USERNAME>,CN=Users,DC=<NAME3>,DC=<NAME2>,DC=<NAME1>" -W -b "CN=Users,DC=<NAME3>,DC=<NAME2>,DC=<NAME1>"  
    Enter LDAP Password:  
    ldap_bind: Strong(er) authentication required (8) 
    additional info: 00002028: LdapErr: DSID-0C090341, comment: The server requires binds to turn on integrity checking if SSL\TLS are not already active on the connection, data 0, v4f7c

Environment

VCF Operations 9.x

Cause

The error Strong(er) authentication required (8) indicates that the Active Directory server enforces strict security policies. It rejects standard, unencrypted LDAP requests (over port 389) and requires a secure authentication method, such as LDAPS or a signed/encrypted bind

Resolution

You can resolve this issue using one of the two options below.

Option 1: Configure LDAPS (Recommended)

Update your VCF SSO identity provider configuration to use LDAPS instead of standard LDAP. This ensures compliance with the Active Directory server's mandatory security requirements. See the official guide: Configure Active Directory as an Identity Provider Using AD/LDAP.

Option 2: Lower Active Directory Security Settings to Accept LDAP Connections (Not Recommended)

Warning: Microsoft does not recommend this approach. Only proceed if you are explicitly authorized by your Active Directory administration team to lower the security posture of the AD server to allow standard, unencrypted LDAP connections.

Since VMware Identity Broker (VIDB) utilizes standard unencrypted simple binds over port 389, the Domain Controller actively rejects the connection payload if strict security rules are enforced. If you must use standard AD/LDAP instead of secure LDAPS, follow the steps below based on your Active Directory version.

For Windows Server AD 2019 and Prior Versions :

Please have your Active Directory administrator follow these exact steps to modify the active Group Policy Object (GPO) to allow unsigned binds:

  1. Open Group Policy Management: On an Active Directory Management Server, press Win + R, type gpmc.msc, and press Enter to open the Group Policy Management Console.

  2. Navigate to the Domain Controllers Policy: Expand the Active Directory Tree by going to: Forest > Domains > [Your Domain Name] > Domain Controllers. Right-click the Default Domain Controllers Policy and select Edit.

  3. Follow the Configuration Tree Path: In the Group Policy Management Editor window, drill down the left tree pane in this exact order:

    Computer Configuration > Policies > Windows Settings > Security Settings > Local Policies > Security Options

  4. Locate the Target Rule: Scroll down the alphabetized list in the right-hand pane and double-click the policy named: Domain controller: LDAP server signing requirements.

  5. Relax Policy Restrictions: Ensure the checkbox Define this policy setting is checked, and use the drop-down menu to change the value from Require signing to None. Click Apply and then OK.

  6. Force a Group Policy Update: Open an administrative Command Prompt (cmd) on the Domain Controller and execute the following command:

    gpupdate /force

    Wait for the terminal to output: "Computer Policy update has completed successfully."

  7. Retry Configuration: Once the policy update completes successfully on the Domain Controllers, please retry saving the Active Directory/LDAP configuration within the VMware Operations SSO configuration details.


For Windows Server AD 2020 and Later Versions :

  1. Open MMC: Open the Microsoft Management Console (MMC) on your Active Directory Windows Server (2020 and later).

  2. Navigate to Security Options: Go to: Domain Control policy > Computer Configuration > Policies > Windows Settings > Security Settings > Local Policies > Security Options.

  3. Modify Security Policies: Update the following policies to the specified values:

    • Domain controller: LDAP server channel binding token requirements – Set to "When Supported"

    • Domain controller: LDAP server signing requirements – Set to "None"

    • Domain controller: LDAP server Enforce signing requirements – Set to "Disabled"

    • Network security: LDAP client encryption requirements – Set to "Negotiate Sealing"

    • Network security: LDAP client signing requirements – Set to "Negotiate Signing"

  4. Force a Group Policy Update: Open an administrative Command Prompt (cmd) on the Domain Controller and execute the following command:

    gpupdate /force

    Wait for the terminal to output: "Computer Policy update has completed successfully."

  5. Retry Configuration: Once the policy update completes successfully on the Domain Controllers, please retry saving the Active Directory/LDAP configuration within the VMware Operations SSO configuration details.