hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benoy Antony (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-10652) Refactor Proxyusers to use AccessControlList
Date Sat, 21 Jun 2014 02:20:25 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-10652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Benoy Antony updated HADOOP-10652:

    Attachment: HADOOP-10652.patch

Thanks for the detailed review, [~daryn].
I believe there will not be incompatibility introduced since {{Groups.getUserToGroupsMappingService}}
 returns the same object irrespective of the configuration passed.
In addition, the {{DefaultImpersonationProvider}} used to invoke {{UserGroupInformation.getGroupNames}},
which used  static variable  - {{groups}. {{groups} is set only once. So the {{Groups}} object
used by {{DefaultImpersonationProvider}} never changed based on newer configuration.

The other comments are taken care of in the attached patch.

> Refactor Proxyusers to use AccessControlList  
> ----------------------------------------------
>                 Key: HADOOP-10652
>                 URL: https://issues.apache.org/jira/browse/HADOOP-10652
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: security
>            Reporter: Benoy Antony
>            Assignee: Benoy Antony
>         Attachments: HADOOP-10652.patch, HADOOP-10652.patch, HADOOP-10652.patch
> Currently Proxyuser specification  accepts a list of users and groups including wildcard
values. Same functionality is already encapsulated in _AccessControlList_ . It will be better
to refactor _ProxyUsers_ to use _AccessControlList_ instead of maintaining separate logic.

This message was sent by Atlassian JIRA

View raw message