VCF Identity Broker encountered an issue during authenticationvIDB-#########.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.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.
Bypass the Load Balancer and reconfigure the external vIDB to point directly to low-latency Domain Controllers (DCs).
SSH to VCF Operations or vCenter Server
Identify two DCs with a network latency of less than 1ms using the ping command:ping <dc-fqdn>
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
Remove the existing external vIDB configuration pointing to the Load Balancer FQDN. Refer to:Cleanup SSO configuration if VCF Identity Broker is down
Reconfigure the external vIDB to point directly to the identified low-latency DCs.
Import the .pem certificate file created in the Step3 into the new external vIDB configuration.
Verify successful authentication by logging into vCenter Server and VCF Operations