I recently integrated vRSLCM to AD server for the users to login to vRSLCM using their AD credentials.
Follow the below steps to add/integrate AD server with vRSLCM:
Login to vRSLCM using admin credentials
Click on Identity and Tenant Management
Then select AD over LDAP from ADD Directory drop down

Fill in the AD server details and add/sync the required users and groups
Once the AD has been integrated you can assign the required permissions to the users

I have assigned all the 4 available permissions to configadmin user
I tried logging into the vRSLCM with configadmin user (AD user) but i got the below error though the user have the admin privilage:

Even the logs was complaining about the permissions.
Post further research and discussion with internal teams I was told to check if the FIPS mode is disabled and when checked the FIPS mode is already disabled under vRSLCM settings.

So for testing purpose I enabled FIPS mode (reboots vRSLCM appliance) and checked if I was able to login to vRSLCM using the same AD user (configadmin), post successful login I disabled the FIPS mode.
Looks like enabling/disabling the FIPS triggers an API which is fixing this.
So as a workaround enable/disable the FIPS mode on your vRSLCM appliance which will help you in fixing the AD user login issue.
Comments