hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Enis Soztutar (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-4348) Adding service-level authorization to Hadoop
Date Tue, 04 Nov 2008 15:44:44 GMT

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

Enis Soztutar updated HADOOP-4348:

    Attachment: jaas_service_v3.patch

Attaching updated patch as a candidate for submission. Differences from previous include improved
javadoc, test cases. 

Here are some points from the patch : 
- introduce HadoopPrincipal, UserPrincipal, GroupPrincipal encapsulating user and group names.

- introduce HadoopPermission as a general permission superclass
- introduce IPCProtocolPermission to indicate a permission for and ipc call of a specific
- introduce ipc.ConnectionHeader, send with once with every ipc connection
- ipc.Client, ipc.Server is changed for new header format. ipc.Server now calls authorize()
for every connection if enabled. 
- proxy methods in ipc.RPC is deprecated to send UUI 
- hadoop daemons(DN, TT, JT, etc) now login as normal users and send UUI for ipc. 
- conf option "mapred.acl.enabled" is deprecated in favor of "hadoop.authorization.enabled".
Later we will change queue acls to jaas-based auth.
- introduced HadoopPolicy as a Policy impl. Reads XML based conf from hadoop-policy.xml 
- introduced SecurityUtil for general purpose security checks.
- added a getSubject() method to UserGroupInformation. 
- TestPermission is renamed to TestFSPermissions

Reviews are more than welcome. 

> Adding service-level authorization to Hadoop
> --------------------------------------------
>                 Key: HADOOP-4348
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4348
>             Project: Hadoop Core
>          Issue Type: New Feature
>            Reporter: Kan Zhang
>            Assignee: Arun C Murthy
>             Fix For: 0.20.0
>         Attachments: HADOOP-4348_0_20081022.patch, jaas_service_v1.patch, jaas_service_v2.patch,
> Service-level authorization is the initial checking done by a Hadoop service to find
out if a connecting client is a pre-defined user of that service. If not, the connection or
service request will be declined. This feature allows services to limit access to a clearly
defined group of users. For example, service-level authorization allows "world-readable" files
on a HDFS cluster to be readable only by the pre-defined users of that cluster, not by anyone
who can connect to the cluster. It also allows a M/R cluster to define its group of users
so that only those users can submit jobs to it.
> Here is an initial list of requirements I came up with.
>     1. Users of a cluster is defined by a flat list of usernames and groups. A client
is a user of the cluster if and only if her username is listed in the flat list or one of
her groups is explicitly listed in the flat list. Nested groups are not supported.
>     2. The flat list is stored in a conf file and pushed to every cluster node so that
services can access them.
>     3. Services will monitor the modification of the conf file periodically (5 mins interval
by default) and reload the list if needed.
>     4. Checking against the flat list is done as early as possible and before any other
authorization checking. Both HDFS and M/R clusters will implement this feature.
>     5. This feature can be switched off and is off by default.
> I'm aware of interests in pulling user data from LDAP. For this JIRA, I suggest we implement
it using a conf file. Additional data sources may be supported via new JIRA's.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message