hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-11341) KMS support for whitelist key ACLs
Date Tue, 02 Dec 2014 11:34:21 GMT

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

Hudson commented on HADOOP-11341:

FAILURE: Integrated in Hadoop-Yarn-trunk-Java8 #23 (See [https://builds.apache.org/job/Hadoop-Yarn-trunk-Java8/23/])
HADOOP-11341. KMS support for whitelist key ACLs. Contributed by Arun Suresh. (wang: rev 31b4d2daa14a7f6e8ee73fd3160e126d8db62ffb)
* hadoop-common-project/hadoop-kms/src/main/java/org/apache/hadoop/crypto/key/kms/server/KMSConfiguration.java
* hadoop-common-project/hadoop-kms/src/main/java/org/apache/hadoop/crypto/key/kms/server/KMSACLs.java
* hadoop-common-project/hadoop-common/CHANGES.txt
* hadoop-common-project/hadoop-kms/src/site/apt/index.apt.vm
* hadoop-common-project/hadoop-kms/src/test/java/org/apache/hadoop/crypto/key/kms/server/TestKMS.java

> KMS support for whitelist key 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
>             Fix For: 2.7.0
>         Attachments: HADOOP-11341.1.patch, HADOOP-11341.2.patch, HADOOP-11341.3.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

View raw message