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 "Xiao Chen (JIRA)" <ji...@apache.org> on 2018/04/09 18:40:00 UTC
[jira] [Updated] (HADOOP-14029) Fix KMSClientProvider for
non-secure proxyuser use case
[ https://issues.apache.org/jira/browse/HADOOP-14029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Xiao Chen updated HADOOP-14029:
-------------------------------
Fix Version/s: 2.8.4
> 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: kms
> Affects Versions: 2.9.0
> Reporter: Xiaoyu Yao
> Assignee: Xiaoyu Yao
> Priority: Major
> Fix For: 2.9.0, 3.0.0-alpha4, 2.8.4
>
> 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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org