What's the difference in using distinguished name with cn or uid when logging into LDAP?

ldap ldapconnection distinguishedname edirectory
jeph perro picture jeph perro · Oct 18, 2011 · Viewed 9.2k times · Source

I'm running into a problem using LDAP to authenticate logins.

We are using a Novell edirectory for authentication of other applications like Jira. ( Jira works perfect ).

I have this application that allow these basic LDAP configurations: enter image description here

My problem is, when I try to log in, it takes my username XXXXXXXX and pre-pends it to the search base as uid. So it tries to log me in as :

uid=XXXXXXXX,ou=people,o=mycompany

Which would work on our Sun LDAP server, but doesn't work on our Novell edirectory LDAP server. edirectory only works when I try to log in as the distinguished name :

cn=XXXXXXXX,ou=people,o=mycompany

Why does edirectory behave like this?

Is it config that we have specified or does edirectory always use cn as distinguished name?

Thanks

Answer

user207421 picture user207421 · Oct 18, 2011

I suggest that is is the application that is 'behaving like this', not edirectory. Obviously your edirectoryis structured differently from your Sun LDAP server, yet the application is treating them both the same. LDAP servers only execute queries, they don't construct them. The application does that.

Related questions

memberOf vs. groupMembership in LDAP (Liferay)

What is the difference b/n memberOf attribute and groupMembership attribute when used in LDAP Authentication settings in Liferay? The users are imported successfully. The groups are also imported successfully. But the users are not assigned to the groups automatically. …

Read More
LDAP: How to authenticate user with connection details

I am not able to authenticate a user using LDAP. I have got following details: URL=ldap://10.10.10.10:389 LDAP BASE:DC=lab2,DC=ins LDAP Bind Account: CN=Ldap Bind,OU=Service Accounts,OU=TECH,DC=lab2,DC=ins LDAP Bind …

Read More
LDAPException when trying to connect using userPrincipalName

We made a new enhancement to the client around LDAP, to enable login using userPrincipalName. He was earlier using sAMAccountName for login. When the user tried to test the application in his test environment, he is getting the following error …

Read More