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 "Zsombor Gegesy (JIRA)" <ji...@apache.org> on 2017/11/01 13:43:00 UTC

[jira] [Updated] (HADOOP-14951) KMSACL implementation is not configurable

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

Zsombor Gegesy updated HADOOP-14951:
------------------------------------
    Attachment: HADOOP-14951-5.patch

Rebased patch

> KMSACL implementation is not configurable
> -----------------------------------------
>
>                 Key: HADOOP-14951
>                 URL: https://issues.apache.org/jira/browse/HADOOP-14951
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: kms
>            Reporter: Zsombor Gegesy
>            Priority: Major
>              Labels: key-management, kms
>         Attachments: 0001-HADOOP-14951-Make-the-KMSACLs-implementation-customi.patch, 0001-Make-the-KMSACLs-implementation-customizable-with-an.patch, HADOOP-14951-3-Make-the-KMSACLs-implementation-customi.patch, HADOOP-14951-4.patch, HADOOP-14951-5.patch
>
>
> Currently, it is not possible to customize KMS's key management, if KMSACLs behaviour is not enough. If an external key management solution is used, that would need a higher level API, where it can decide, if the given operation is allowed, or not.
>  For this to achieve, it would be a solution, to introduce a new interface, which could be implemented by KMSACLs - and also other KMS - and a new configuration point could be added, where the actual interface implementation could be specified.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org