ranger-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anant Aneja (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (RANGER-1735) Support representing nested group memberships in Ranger Admin
Date Tue, 22 May 2018 20:58:00 GMT

    [ https://issues.apache.org/jira/browse/RANGER-1735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16484560#comment-16484560

Anant Aneja commented on RANGER-1735:

[~spolavarapu] I just re-read my question and I realized I made a mistake. I'veĀ edited my
question now. Can you re-evaluate if the answer you gave is still correct ?

> 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
>            Priority: Major
>             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

View raw message