hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-14951) KMSACL implementation is not configurable
Date Tue, 17 Oct 2017 07:01:00 GMT

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

Hadoop QA commented on HADOOP-14951:
------------------------------------

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m  0s{color} | {color:blue}
Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red}  0m  4s{color} | {color:red}
HADOOP-14951 does not apply to trunk. Rebase required? Wrong Branch? See https://wiki.apache.org/hadoop/HowToContribute
for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HADOOP-14951 |
| JIRA Patch URL | https://issues.apache.org/jira/secure/attachment/12892543/0001-Make-the-KMSACLs-implementation-customizable-with-an.patch
|
| Console output | https://builds.apache.org/job/PreCommit-HADOOP-Build/13527/console |
| Powered by | Apache Yetus 0.6.0-SNAPSHOT   http://yetus.apache.org |


This message was automatically generated.



> 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
>              Labels: key-management, kms
>         Attachments: 0001-HADOOP-14951-Make-the-KMSACLs-implementation-customi.patch,
0001-Make-the-KMSACLs-implementation-customizable-with-an.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


Mime
View raw message