You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ranger.apache.org by "Sailaja Polavarapu (JIRA)" <ji...@apache.org> on 2017/09/07 21:33:00 UTC
[jira] [Commented] (RANGER-1735) Support representing nested group
memberships in Ranger Admin
[ https://issues.apache.org/jira/browse/RANGER-1735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16157683#comment-16157683 ]
Sailaja Polavarapu commented on RANGER-1735:
--------------------------------------------
Committed changes to master.
> Support representing nested group memberships in Ranger Admin
> -------------------------------------------------------------
>
> Key: RANGER-1735
> URL: https://issues.apache.org/jira/browse/RANGER-1735
> Project: Ranger
> Issue Type: New Feature
> Components: Ranger, usersync
> Affects Versions: 0.7.1
> Reporter: Sailaja Polavarapu
> Assignee: Sailaja Polavarapu
> Fix For: 1.0.0, 0.7.2
>
> Attachments: 0001-RANGER-1735-Support-representing-nested-group-member.patch, Ranger Usersync - Nested Group Support.docx
>
>
> Several large enterprises have their groups in LDAP/AD nested within other groups. Since Ranger user sync currently only pulls in the immediate group, it is possible that some nested memberships might not be available for policy authoring. Hadoop user-group mapping already supports nested LDAP/AD groups for policy enforcement at the Ranger plugin.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)