Support Questions

Find answers, ask questions, and share your expertise
Announcements
Celebrating as our community reaches 100,000 members! Thank you!

Not able to login to Ambari using LDAP User

avatar
Super Collaborator

Hi All, I synced some users from IPA LDAP to Ambari. However I am not able to login to ambari using any of the LDAP users. On the web UI I get the below error,

Unable to connect to Ambari Server. 

Confirm Ambari Server is running and you can reach Ambari Server from this machine.

ambari-server.txt Also attached the exception trace.

1 ACCEPTED SOLUTION

avatar
Super Collaborator

Started working now. Below are the changes I made

New Values

authentication.ldap.userObjectClass=person
authentication.ldap.usernameAttribute=uid

Old Values

authentication.ldap.userObjectClass=mepManagedEntry
authentication.ldap.usernameAttribute=cn

View solution in original post

7 REPLIES 7

avatar
Master Guru

It looks like there are 2 users called "arun". Can you try to restart ambari-server, login as admin and check regiestered users.

avatar
Super Collaborator

@Predrag Minovic I did verify that. There is only 1 user arun within the directory. Tried restarting the server, still the same.

avatar
Super Guru

@Arun A K

Before bringing new user records from LDAP to Ambari, did you have an Ambari user Arun?

avatar
Super Collaborator

Hi @Constantin Stanca, there wasn't multiple user by the name Arun. However after changing the default values for userObjectClass and usernameAttribute, I got it working.

avatar
Super Collaborator

Started working now. Below are the changes I made

New Values

authentication.ldap.userObjectClass=person
authentication.ldap.usernameAttribute=uid

Old Values

authentication.ldap.userObjectClass=mepManagedEntry
authentication.ldap.usernameAttribute=cn

avatar
Super Collaborator

The only problem here is that the user list specified while sync'ing need to have the uid rather than the user name.

avatar
Super Collaborator

Not Sure why, but when a user "x" was created in IPA, there was an entry for x under users and also under groups. Could be this lead to ambiguity for the search to locate the right user "x" (arun in my case). To resolve the ambiguity, I thought of referring users by their uid rather than the default cn, which could conflict.

7005-ipa.png