[
https://issues.apache.org/jira/browse/HADOOP-4348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12644039#action_12644039
]
Enis Soztutar commented on HADOOP-4348:
---------------------------------------
@Sanjay
bq. 1. rather then invent new authorization layers use JAAS
bq. 2. we should have used JAAS in the first place when we did UGI.
Exactly.
@Arun, @Sanjay
Yes I also share the wisdom that enabling security manager is an overkill, and
the policy file's syntax is ugly.
I am attaching a patch for review which does the job, w/o enabling security
manager. The actual security manager's implementation is to delegate all the
work to AccessController. The patch uses accesscontroller directly so SM is not
explicitly enabled. With this schema, security checks only occur as in the
patch. AFAIK, all the core java code use SM, and since it is not enabled,
performance does not suffer. Of course we should check this before patch is
committed.
Patch introduces a HaddopPolicy implementation, which reads its configuration
from an XML file. The schema of the file is relatively simple, and extensible
for further JAAS based authorization checks. Unfortunately, the
permissions/principals model does not fit perfectly to be configured in the
property based configuration files, so I guess we have to include a new format.
> 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.
