Connectors fail to communicate with AD in VMware Identity Manager
search cancel

Connectors fail to communicate with AD in VMware Identity Manager

book

Article ID: 451724

calendar_today

Updated On:

Products

VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

  • VMware Identity Manager (vIDM) UI cannot be accessed across two cluster nodes through the NSX Load Balancer.
  • Error appears:
    Something failed and we cannot load the screen you were about to view. You can check logs for possible causes
    After accessing the vIDM configuration page directly via port 8443. (https://<REDACTED_FQDN>:8443)
  • Attempting to execute the Re-Trust Load Balancer operation from Aria Suite Lifecycle (LCM), it fails with the error LCMVIDM71077. 

Environment

  • VMware Identity Manager 3.3.7 (CSP-102547 applied)
  • VMware Aria Suite Lifecycle 8.18.0 patch 8

Cause

Corrupted Active Directory identity provider directory profile binding state within VMware Identity Manager preventing proper cluster-wide authentication routing across the load balancer nodes.

Resolution

  1. Verify that the SSL certificate SAN fields match identically across all vIDM nodes and the load balancer VIP.

  2. Perform certificate replacement on the NSX Load Balancer by following How to replace a vIDM cluster load balancer certificate in NSX-T and update Aria Suite Lifecycle.

  3. Resolve port 8443 access errors by updating missing configuration parameters in /usr/local/horizon/conf/system-config.properties on all affected nodes following Accessing the configuration settings page over port 8443 does not fully load or throws an error.

  4. Retry the Re-Trust Load Balancer task from Aria Suite Lifecycle to confirm success.

  5. Log in to the vIDM Administration Console as an administrator: https://<REDACTED_FQDN>/SAAS/admin.

  6. Navigate to Identity & Access Management > Manage > Directories.

  7. Record the existing Active Directory domain configuration settings.(Domain Name, Bind DN, Host Servers, Base DN, Sync Settings).

  8. Remove the Active Directory profile from vIDM.

  9. Re-add the Active Directory profile using the saved configuration details.

  10. Verify that all vIDM cluster nodes are accessible through the NSX Load Balancer UI.

Powered by Wolken Software