[
https://issues.apache.org/jira/browse/HADOOP-11046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14118383#comment-14118383
]
Allen Wittenauer commented on HADOOP-11046:
-------------------------------------------
Pre-emptive, as I prefer KMS's. :)
> 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)
