Aria Identity Manager fails to connect to Active Directory after upgrading to GRUB 2.0 and applying CSP-97577.

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

After upgrading to GRUB 2.0 and applying patch CSP-97577 to VMware Identity Manager (vIDM), Aria Identity Manager fails to connect to Active Directory. Users attempting to configure or sync Active Directory experience a connection failure.

The following error message is prominently displayed in the UI:
"Connector communication failed because of invalid data: The specified Bind DN and password could not be used to successfully authenticate against the directory."

Environment

VMware Identity Manager 3.3.7 with CSP-97577 installed.

Resolution

Resolution Steps:

1. If VIDM is deployed in FIPS mode
   
   1. Check the File Permission
      ls -lrth /opt/vmware/horizon/workspace/conf/idm_fips.security
      Example:
      -r--r----- 1 horizon www 847 Aug 22 09:42 /opt/vmware/horizon/workspace/conf/idm_fips.security
   2. Take the backup of the file
            cp /opt/vmware/horizon/workspace/conf/idm_fips.security /opt/vmware/horizon/workspace/conf/idm_fips.security.bak
   3. Copy the attached file[idm_fips.security] to vIDM Node/Nodes and replace
           cp [idm_fips.security] /opt/vmware/horizon/workspace/conf/
   4. Check the file permission and set as per step 1. a (chmod 440 <filename>)
      
      
2. If VIDM is deployed in Non FIPS mode
   1. Check the File Permission
      ls -lrth /opt/vmware/horizon/workspace/conf/idm_non_fips.security
      Example:
      -r--r----- 1 horizon www 847 Aug 22 09:42 /opt/vmware/horizon/workspace/conf/idm_non_fips.security
   2. Take the backup of the file
            cp /opt/vmware/horizon/workspace/conf/idm_non_fips.security /opt/vmware/horizon/workspace/conf/idm_non_fips.security.bak
   3. Copy the attached file[idm_non_fips.security] to vIDM Node/Nodes and replace
           cp [idm_non_fips.security] /opt/vmware/horizon/workspace/conf/
   4. Check the file permission and set as per step 2. a (chmod 440 <filename>)