[
https://issues.apache.org/jira/browse/HADOOP-4348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12642278#action_12642278
]
Sanjay Radia commented on HADOOP-4348:
--------------------------------------
Eris,
I think your point is:
# rather then invent new authorization layers use JAAS
# we should have used JAAS in the first place when we did UGI.
When we did permissions/UGI we did look at JAAS briefly but due to time
pressures we went with our own impl. Our feeling was to reexamine this later.
Basically we set the UGI context in a thread local variable. JAAS does the same.
I think the rest of the debate in this jira about which layer (ipc or rpc) to
use still stands.
JAAS does support the per call authorization; don''t know if JAAS supports
session level authorization when the session is created. However, JAAS combined
with GSS does authentication at the connection level.
If we use Jaas then
# we should not turn on the java security manager - it is not needed and it is
expensive
# we should not put the acl in the java security policy file - the policy file
syntax is complex and not necessary for us.
I believe JMX used JAAS and it does not turn on the security manager and
further puts the ACL in a separate file ( I will verify if JMX used JAAS).
> 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
>
>
> 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.
