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

本秂侑毒 提交于 2019-12-01 17:55:23

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.

The naming attribute is up to the person making the object. However by default most eDirectory tools set it as cn=. If you want, you can create objects as uid= in your eDirectory. It would be hard to convert existing users.

Many LDAP tools that make this assumption will allow you to specify what the naming attribute might be.

Your app is making a bad assumption.

You can add a UID value on each object, the same as the CN, but that would not help since it is not then a naming attribute.

In other words, if the application was doing a query for (uid=XXXXXXXX) then adding a uid value that matches CN would help.

If however it is doing a bind as a specific user, as uid=XXXXXXXX,ou=users,o=mycompany that won't help.

易学教程内所有资源均来自网络或用户发布的内容,如有违反法律规定的内容欢迎反馈
该文章没有解决你所遇到的问题?点击提问,说说你的问题,让更多的人一起探讨吧!