Return-Path: 
 <common-issues-return-72953-apmail-hadoop-common-issues-archive=hadoop.apache.org@hadoop.apache.org>
X-Original-To: apmail-hadoop-common-issues-archive@minotaur.apache.org
Delivered-To: apmail-hadoop-common-issues-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id AD3C210DC9
	for <apmail-hadoop-common-issues-archive@minotaur.apache.org>;
 Thu, 27 Nov 2014 22:43:13 +0000 (UTC)
Received: (qmail 99921 invoked by uid 500); 27 Nov 2014 22:43:13 -0000
Delivered-To: apmail-hadoop-common-issues-archive@hadoop.apache.org
Received: (qmail 99792 invoked by uid 500); 27 Nov 2014 22:43:13 -0000
Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:common-issues-help@hadoop.apache.org>
List-Unsubscribe: <mailto:common-issues-unsubscribe@hadoop.apache.org>
List-Post: <mailto:common-issues@hadoop.apache.org>
List-Id: <common-issues.hadoop.apache.org>
Reply-To: common-issues@hadoop.apache.org
Delivered-To: mailing list common-issues@hadoop.apache.org
Received: (qmail 99534 invoked by uid 99); 27 Nov 2014 22:43:12 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 27 Nov 2014 22:43:12 +0000
Date: Thu, 27 Nov 2014 22:43:12 +0000 (UTC)
From: "Arun Suresh (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <JIRA.12758056.1417032808000.36798.1417128192856@Atlassian.JIRA>
In-Reply-To: <JIRA.12758056.1417032808000@Atlassian.JIRA>
References: <JIRA.12758056.1417032808000@Atlassian.JIRA>
 <JIRA.12758056.1417032808074@arcas>
Subject: [jira] [Updated] (HADOOP-11341) Add support for root key KMS ACLs
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


     [ https://issues.apache.org/jira/browse/HADOOP-11341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Arun Suresh updated HADOOP-11341:
---------------------------------
    Issue Type: New Feature  (was: Bug)

> Add support for root key KMS ACLs
> ---------------------------------
>
>                 Key: HADOOP-11341
>                 URL: https://issues.apache.org/jira/browse/HADOOP-11341
>             Project: Hadoop Common
>          Issue Type: New Feature
>          Components: kms, security
>            Reporter: Arun Suresh
>            Assignee: Arun Suresh
>         Attachments: HADOOP-11341.1.patch, HADOOP-11341.2.patch
>
>
> As reported by [~dian.fu] :
> Key based ACL in KMS is currently implemented as whitelist. So if I configure as follows in kms-acl.xml,
> {code}
>  <property>
>     <name>key.acl.testKey.DECRYPT_EEK</name>
>     <value>testUser</value>
>   </property>
> {code}, then only {{testUser}} user can do {{DECRYPT_EEK}} call on key {{testKey}}. If I want {{yarn}} user can also do {{DECRYPT_EEK}} call on {{testKey}} key, I need add {{yarn}} user to the above configuration value manually. This means that if I want to configure key based ACL({{DECRYPT_EEK}}) for {{some key}}, I need also add {{yarn}} user to configuration {{DECRYPT_EEK}} for that key. As I don't know if {{yarn}} user will later need to do {{DECRYPT_EEK}} for this key.. This is inconvenient and tricky.
> This can be alleviated by slightly modifying the key ACL logic in KMS first checks if the user, in this case {{yarn}}, is present in {{key.acl.<key-name>.<OP-name>}} list. And if not, then also check if the user is present in {{default.key.acl.<OP-name>}}. If yes, then grant access.. else deny.
> Currently,  {{default.key.acl.<OP-name>}} is consulted only if NO {{key.acl.<key-name>.<OP-name>}} is specified.



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