hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alejandro Abdelnur (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-11046) Normalize ACL configuration property across hadoop components
Date Tue, 02 Sep 2014 16:55:21 GMT

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

Alejandro Abdelnur commented on HADOOP-11046:
---------------------------------------------

[~aw], why an incompat change? KMS has not made it to any release yet.

> Normalize ACL configuration property across hadoop components
> -------------------------------------------------------------
>
>                 Key: HADOOP-11046
>                 URL: https://issues.apache.org/jira/browse/HADOOP-11046
>             Project: Hadoop Common
>          Issue Type: Bug
>    Affects Versions: 3.0.0
>            Reporter: Arun Suresh
>            Assignee: Arun Suresh
>
> Service authorization policies has different naming convention for ACLS and blacklists
compared to KMS ACLS.
> *Sample Service authorization ACL entry keys*
> {noformat}
> security.refresh.user.mappings.protocol.acl 
> security.refresh.user.mappings.protocol.acl.blocked (blacklists)
> {noformat}
> *Sample KMS ACL entry keys*
> {noformat}
> hadoop.kms.acl.CREATE 
> hadoop.kms.blacklist.CREATE
> {noformat}
> We need to follow a uniform naming scheme for both types of ACLs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message