[jira] [Commented] (AMBARI-7537) Admin : LDAP skipped group memberships

["Hudson (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AMBARI-7537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14151723#comment-14151723 ] 

Hudson commented on AMBARI-7537:
--------------------------------

FAILURE: Integrated in Ambari-trunk-Commit #406 (See [https://builds.apache.org/job/Ambari-trunk-Commit/406/])
AMBARI-7537 - Admin : LDAP skipped group memberships (tbeerbower: http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=cfc7347ff7741319e2f2ae27537534a51c0a7e17)
* ambari-server/src/test/java/org/apache/ambari/server/security/ldap/AmbariLdapDataPopulatorTest.java
* ambari-server/src/main/java/org/apache/ambari/server/security/ldap/AmbariLdapDataPopulator.java


> Admin : LDAP skipped group memberships
> --------------------------------------
>
>                 Key: AMBARI-7537
>                 URL: https://issues.apache.org/jira/browse/AMBARI-7537
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Tom Beerbower
>            Assignee: Tom Beerbower
>             Fix For: 1.7.0
>
>
> In the case where group membership is defined by an attribute like this ...
> {code}
> uniqueMember
>     uid=tesla,dc=example,dc=com
>     uid=newton,dc=example,dc=com
> ...
> {code}
> The code assumes that the attribute value will be a simple, single value like 'tesla' or 'newton', so the filter is not constructed properly for the case above.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)