hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Allen Wittenauer (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-6634) AccessControlList uses full-principal names to verify acls causing queue-acls to fail
Date Wed, 17 Mar 2010 14:00:27 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-6634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12846421#action_12846421
] 

Allen Wittenauer commented on HADOOP-6634:
------------------------------------------

Hopefully ACLs will get updated to support both plain "user" and a principal name.  This way
we could force automated jobs that use cron/user (or whatever) to go to a special queue vs.
ad hoc queries going to a different queue.

> AccessControlList uses full-principal names to verify acls causing queue-acls to fail
> -------------------------------------------------------------------------------------
>
>                 Key: HADOOP-6634
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6634
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: security
>            Reporter: Vinod K V
>             Fix For: 0.22.0
>
>
> ACL configuration so far was using short user-names. With the changed {{UserGroupInformation}},
short names are different from the long fully-qualified names. {{AccessControlList}} continues
to use {{UserGroupInformation.getUserName()}} for verifying access control. Because of this,
queue acls fail for a user "user@domain.org" even though the short name "user" is part of
the acl configuration.

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


Mime
View raw message