[
https://issues.apache.org/jira/browse/HADOOP-4348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12642224#action_12642224
]
Enis Soztutar commented on HADOOP-4348:
---------------------------------------
Sorry for coming late, but I am not in favor of implementing a custom
authorization solution. I have been looking into JAAS lately and it seems a
perfect fit for our needs. I guess incremental updates to JAAS based
authorization and authentication can solve
this issue, HADOOP-4490, HADOOP-4487 and all of the subissues.
For authorization we can plug current Unix based implementation for now, but
once implemented HADOOP-1741 will fit the framework seamlessly.
And for access control, we can implement permission implementations for any
type of operation. For example we can have ConnectionPermission to check to IPC
connections, and RPCProtocolPermission for RPC protocol name permissions.
With JAAS we can implement user based access control easily by running the code
with the user's privileges, we can check for user's not killing each others
job, etc.
We can achieve authentication/authorization independency. We can just continue
to work on access control with unixugi, and introduce kerberos based
authentication w/o changing any authentication code at all.
> 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
>
>
> 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.
