"VCF Identity Broker encountered an issue during authentication" error in VCF Operations and vCenter Server
search cancel

"VCF Identity Broker encountered an issue during authentication" error in VCF Operations and vCenter Server

book

Article ID: 439247

calendar_today

Updated On:

Products

VCF Operations VMware vSphere ESXi

Issue/Introduction

  • Domain logins for VMware Cloud Foundation Operations and vCenter Server fail with the following error:
    VCF Identity Broker encountered an issue during authentication


  • Active Directory over LDAPS configurations, the error appears immediately following a successful DUO Multi-Factor Authentication (MFA) prompt.

  • Initial login attempts fail, but access is granted after multiple browser refreshes.

  • vIDB-#########.log files indicate a communication timeout between the system and the Load Balancer attempting to reach the backend Domain Controllers (DCs)..
    ERROR vidb-service-#######-dnrqz:usergroup (usergroup-business-pool-0) [CUSTOMER;#####-###-###-###-###;##.##.##.##;###-##-##-##-##;-] com.vmware.vidm.usergroup.service.broker.connector.ActiveDirectoryServiceImpl - Connecting to Active Directory on socket (load balancer fqdn:636) has timed out.

Cause

High network latency between the Load Balancer and the Domain Controllers causes authentication requests to exceed the timeout limits in VCFOperations, vIDB, and vCenter Server. Consequently, the system drops the requests and triggers the authentication error.

Resolution

Bypass the Load Balancer and reconfigure the external vIDB to point directly to low-latency Domain Controllers (DCs).

  1. SSH to VCF Operations or vCenter Server

  2. Identify two DCs with a network latency of less than 1ms using the ping command:
    ping <dc-fqdn>

  3. Retrieve the SSL certificates from the identified DCs using the openssl command. Copy the certificate output into a notepad and save the file in .pem format:
    Example:
    openssl s_client -showcerts -connect <dc-fqn>:636

  4. Remove the existing external vIDB configuration pointing to the Load Balancer FQDN. Refer to:Cleanup SSO configuration if VCF Identity Broker is down

  5. Reconfigure the external vIDB to point directly to the identified low-latency DCs.

  6. Import the .pem certificate file created in the Step3 into the new external vIDB configuration.

  7. Verify successful authentication by logging into vCenter Server and VCF Operations

Additional Information

Configuring VCF Single Sign-On
Bringing “Out-of-the-Box” Modern Identity to Your Infrastructure with VMware Cloud Foundation 9.0
Error: "Access Denied" after PingID MFA for VCF SSO
Generating and downloading support logs for Identity Broker in VCF 9