[
https://issues.apache.org/jira/browse/HADOOP-8121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13228502#comment-13228502
]
Jonathan Natkins commented on HADOOP-8121:
------------------------------------------
a) I'm a little unclear under what circumstances you expect this to hit a
search limit. Would you expect that users would belong to more groups than the
search limit can support in a single search? That seems surprising to me. Like
I said earlier, if the plug-in is misconfigured, and you have a search filter
that is not sensible, say (objectClass=*), yes, you would probably hit a search
limit. In that case, an exception would be through in getGroups, and logged,
alerting an admin to the fact that there's a problem.
b) You're right, I'll document this somewhere.
Regarding documentation, where is the most appropriate place for it to go?
> Active Directory Group Mapping Service
> --------------------------------------
>
> Key: HADOOP-8121
> URL: https://issues.apache.org/jira/browse/HADOOP-8121
> Project: Hadoop Common
> Issue Type: New Feature
> Components: security
> Reporter: Jonathan Natkins
> Assignee: Jonathan Natkins
> Attachments: HADOOP-8121.patch, HADOOP-8121.patch, HADOOP-8121.patch,
> HADOOP-8121.patch, HADOOP-8121.patch, HADOOP-8121.patch, HADOOP-8121.patch,
> HADOOP-8121.patch, HADOOP-8121.patch
>
>
> Planning on building a group mapping service that will go and talk directly
> to an Active Directory setup to get group memberships
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
