[
https://issues.apache.org/jira/browse/HADOOP-11482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14290652#comment-14290652
]
Hudson commented on HADOOP-11482:
---------------------------------
FAILURE: Integrated in Hadoop-Mapreduce-trunk-Java8 #84 (See
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Java8/84/])
HADOOP-11482. Use correct UGI when KMSClientProvider is called by a proxy user.
Contributed by Arun Suresh. (wang: rev 4b00935643f6c3656ccbd7eeb54884738bc12c2e)
*
hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/crypto/key/kms/KMSClientProvider.java
*
hadoop-common-project/hadoop-kms/src/test/java/org/apache/hadoop/crypto/key/kms/server/TestKMS.java
* hadoop-common-project/hadoop-common/CHANGES.txt
> Use correct UGI when KMSClientProvider is called by a proxy user
> ----------------------------------------------------------------
>
> Key: HADOOP-11482
> URL: https://issues.apache.org/jira/browse/HADOOP-11482
> Project: Hadoop Common
> Issue Type: Bug
> Affects Versions: 2.6.0
> Reporter: Arun Suresh
> Assignee: Arun Suresh
> Fix For: 2.7.0
>
> Attachments: HADOOP-11482.1.patch, HADOOP-11482.2.patch
>
>
> Long Living clients of HDFS (For eg. OOZIE) use cached DFSClients which in
> turn use a cached KMSClientProvider to talk to KMS.
> Before an MR Job is run, the job client calls the
> {{DFClient.addDelegationTokens()}} method which calls
> {{addDelegationTokens()}} on the {{KMSClientProvider}} to get any delegation
> token associated to the user.
> Unfortunately, this call uses a cached
> {{DelegationTokenAuthenticationURL.Token}} instance which can cause the
> {{SignerSecretProvider}} implementation of the {{AuthenticationFilter}} at
> the KMS Server end to fail validation. Which results in the MR job itself
> failing.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
