登录LDAP时，将专有名称与cn或uid一起使用有什么区别? [英] What's the difference in using distinguished name with cn or uid when logging into LDAP?

问题描述

使用LDAP对登录进行身份验证时遇到问题.

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

我们正在使用Novell电子目录对其他应用程序(如Jira)进行身份验证. (Jira完美).

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

我有一个允许以下基本LDAP配置的应用程序:

I have this application that allow these basic LDAP configurations:

我的问题是，当我尝试登录时，它将使用我的用户名XXXXXXXX并将其作为uid附加到搜索库中.因此它尝试以以下身份登录我:

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

uid=XXXXXXXX,ou=people,o=mycompany

哪些可以在我们的Sun LDAP服务器上使用，但不能在我们的Novell edirectory LDAP服务器上使用.只有当我尝试使用专有名称登录时，edirectory才有效:

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

cn=XXXXXXXX,ou=people,o=mycompany

为什么电子目录的行为如此?

Why does edirectory behave like this?

是我们指定的配置，还是edirectory始终使用cn作为专有名称?

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

谢谢

推荐答案

我建议这是行为类似"的应用程序，而不是edirectory.显然，您的edirectory的结构与Sun LDAP服务器的结构不同，但是应用程序将两者相同. LDAP服务器仅执行查询，而不构造查询.该应用程序将执行此操作.

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.

这篇关于登录LDAP时，将专有名称与cn或uid一起使用有什么区别?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！