[ https://issues.apache.org/jira/browse/HADOOP-12001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14567683#comment-14567683 ]
Vinod Kumar Vavilapalli commented on HADOOP-12001: -------------------------------------------------- bq. I'm new to patches in Hadoop, what additional work is required on the patch? bq. For testing, I've run it on a cluster and verified I see the right thing when configured in posixGroups mode with the 'groups' command. I'm not 100% sure how to modify the unit tests to fit this case, but haven't looked very deeply yet. I looked at the patch. Seems compatible, that part looks good. Can you see TestLdapGroupsMapping and TestLdapGroupsMappingWithPosixGroup and look if you can add a test there? > Limiting LDAP search conflicts with posixGroup addition > ------------------------------------------------------- > > Key: HADOOP-12001 > URL: https://issues.apache.org/jira/browse/HADOOP-12001 > Project: Hadoop Common > Issue Type: Bug > Components: security > Affects Versions: 2.7.0, 2.8.0 > Reporter: Patrick White > Assignee: Patrick White > Priority: Blocker > Attachments: HADOOP-12001.patch > > > In HADOOP-9477, posixGroup support was added > In HADOOP-10626, a limit on the returned attributes was added to speed up > queries. > Limiting the attributes can break the SEARCH_CONTROLS object in the context > of the isPosix block, since it only asks LDAP for the groupNameAttr -- This message was sent by Atlassian JIRA (v6.3.4#6332)