[
https://issues.apache.org/jira/browse/AMBARI-10020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14357047#comment-14357047
]
Hudson commented on AMBARI-10020:
---------------------------------
SUCCESS: Integrated in Ambari-trunk-Commit #2004 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/2004/])
AMBARI-10020 - Ambari Server sync-ldap not pulling in group membership
(tbeerbower) (tbeerbower:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=91ca6666d8862029882abf806e32dab051167d9c)
*
ambari-server/src/main/java/org/apache/ambari/server/security/ldap/AmbariLdapDataPopulator.java
*
ambari-server/src/test/java/org/apache/ambari/server/security/ldap/AmbariLdapDataPopulatorTest.java
> Ambari Server sync-ldap not pulling in group membership
> -------------------------------------------------------
>
> Key: AMBARI-10020
> URL: https://issues.apache.org/jira/browse/AMBARI-10020
> Project: Ambari
> Issue Type: Bug
> Reporter: Tom Beerbower
> Assignee: Tom Beerbower
> Fix For: 2.1.0
>
> Attachments: AMBARI-10020.patch
>
>
> The filter being used for group membership is wrong.
> We should be capturing and re-using DN's for the group membership lookup as
> part of the user import process.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)