登录 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

为什么 edirectory 会这样?

Why does edirectory behave like this?

是我们指定的config还是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屋！