Video Screencast Help

VOM - User LDAP authentication

Created: 26 Apr 2011 • Updated: 29 Apr 2011 | 1 comment
BCAM's picture
1 Agree
0 Disagree
+1 1 Vote
Login to vote
Status: On Roadmap

The AD server that is used in the LDAP/AD configuration requires an account to login and was configured as such. I realized that the account that was used to configure LDAP/AD, had a password change and this broke the authentication when the account was attempting to broker the authentication with the AD controller and hence caused this issue.

I had to basically remove the ‘Domain’ entry in ‘Authentication Broker’ page in the managed server and recreate the new ones using the updated AD user/password and the authentication is working as expected.

So there are few things that would have been useful to investigate this

1)      Verbose logging, if there was an AD error indicating an authentication failure, would have been easier to investigate.

2)      Ability to modify the existing ‘Domain’ configuration to update the changed password instead of recreating the same entry. In an complex AD environment as ours, this option to update the password will be very valuable and please submit an RFE (Request for enhancement). 

Comments 1 CommentJump to latest comment

CMilani's picture

Thank you for identifying this issue. I will included it in the product roadmap.

Login to vote