[
https://issues.apache.org/jira/browse/HADOOP-10611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14014358#comment-14014358
]
Hudson commented on HADOOP-10611:
---------------------------------
SUCCESS: Integrated in Hadoop-trunk-Commit #5636 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/5636/])
HADOOP-10611. KMS, keyVersion name should not be assumed to be
keyName@versionNumber. (tucu) (tucu:
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1598775)
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
*
/hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/crypto/key/kms/KMSClientProvider.java
*
/hadoop/common/trunk/hadoop-common-project/hadoop-kms/src/main/java/org/apache/hadoop/crypto/key/kms/server/KMSCacheKeyProvider.java
*
/hadoop/common/trunk/hadoop-common-project/hadoop-kms/src/test/java/org/apache/hadoop/crypto/key/kms/server/TestKMS.java
> KMS, keyVersion name should not be assumed to be keyName@versionNumber
> ----------------------------------------------------------------------
>
> Key: HADOOP-10611
> URL: https://issues.apache.org/jira/browse/HADOOP-10611
> Project: Hadoop Common
> Issue Type: Bug
> Components: security
> Affects Versions: 3.0.0
> Reporter: Alejandro Abdelnur
> Assignee: Alejandro Abdelnur
> Fix For: 3.0.0
>
> Attachments: HADOOP-10611.patch
>
>
> Some KMS classes are assuming the keyVersion is keyName@versionNumber.
> The keyVersion should be handled as an opaque value.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
