[
https://issues.apache.org/jira/browse/AMBARI-13943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15032732#comment-15032732
]
Hudson commented on AMBARI-13943:
---------------------------------
FAILURE: Integrated in Ambari-branch-2.1 #970 (See
[https://builds.apache.org/job/Ambari-branch-2.1/970/])
AMBARI-13943. Ambari LDAP integration cannot handle LDAP directories
(rnettleton:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=589b7c60cd2ef4d2001755c079ddf38c8418c82e])
*
ambari-server/src/test/java/org/apache/ambari/server/security/authorization/LdapServerPropertiesTest.java
*
ambari-server/src/main/java/org/apache/ambari/server/security/authorization/LdapServerProperties.java
> Ambari LDAP integration cannot handle LDAP directories with multiple entries
> for the same user
> ----------------------------------------------------------------------------------------------
>
> Key: AMBARI-13943
> URL: https://issues.apache.org/jira/browse/AMBARI-13943
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.1.1
> Reporter: Olivér Szabó
> Assignee: Olivér Szabó
> Priority: Critical
> Fix For: 2.1.3
>
> Attachments: AMBARI-13943.patch
>
>
> For user search, ambari uses only uid in the user search filter. Spring ldap
> template cannot handle multiple result entries, because UID is not unique,
> therefore users can not login into ambari UI
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
