[
https://issues.apache.org/jira/browse/HADOOP-14029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15841020#comment-15841020
]
Hudson commented on HADOOP-14029:
---------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #11183 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/11183/])
HADOOP-14029. Fix KMSClientProvider for non-secure proxyuser use case. (xyao:
rev 2034315763cd7b1eb77e96c719918fc14e2dabf6)
* (edit)
hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/crypto/key/kms/KMSClientProvider.java
* (edit)
hadoop-common-project/hadoop-kms/src/test/java/org/apache/hadoop/crypto/key/kms/server/TestKMS.java
> Fix KMSClientProvider for non-secure proxyuser use case
> -------------------------------------------------------
>
> Key: HADOOP-14029
> URL: https://issues.apache.org/jira/browse/HADOOP-14029
> Project: Hadoop Common
> Issue Type: Bug
> Components: common,kms
> Affects Versions: 2.9.0
> Reporter: Xiaoyu Yao
> Assignee: Xiaoyu Yao
> Fix For: 2.9.0, 3.0.0-alpha3
>
> Attachments: HADOOP-14029.00.patch, HADOOP-14029.01.patch
>
>
> The issue was found after HADOOP-13988 by Hadoop-HDFS test
> (TestAclsEndToEnd). Sorry both Jenkins and I was not able to catch it.
> HADOOP-13988 fixed the issue for KMSClientProvider secure proxy user(token)
> use case. But the non-secure proxy user case should not be affected by the
> new logic. The ticket is open to fix it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
