You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Alejandro Abdelnur (JIRA)" <ji...@apache.org> on 2014/09/02 18:55:21 UTC
[jira] [Commented] (HADOOP-11046) Normalize ACL configuration
property across hadoop components
[ 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)