hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zsombor Gegesy (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-14951) KMSACL implementation is not configurable
Date Thu, 02 Nov 2017 14:01:00 GMT

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

Zsombor Gegesy commented on HADOOP-14951:

The test failures shouldn't be related to the changed code.

> 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

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

View raw message