[
https://issues.apache.org/jira/browse/HADOOP-11069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14123582#comment-14123582
]
Hadoop QA commented on HADOOP-11069:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12666874/HADOOP-11069.patch
against trunk revision 0571b45.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
hadoop-common-project/hadoop-common hadoop-common-project/hadoop-kms:
org.apache.hadoop.crypto.key.kms.server.TestKMS
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/4660//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/4660//console
This message is automatically generated.
> KMSClientProvider should use getAuthenticationMethod() to determine if in
> proxyuser mode or not
> -----------------------------------------------------------------------------------------------
>
> Key: HADOOP-11069
> URL: https://issues.apache.org/jira/browse/HADOOP-11069
> Project: Hadoop Common
> Issue Type: Bug
> Components: security
> Affects Versions: 2.6.0
> Reporter: Alejandro Abdelnur
> Assignee: Alejandro Abdelnur
> Attachments: HADOOP-11069.patch
>
>
> Currently is checking the login UGI being different from the current UGI, it
> should check if the current UGI auth method is PROXY.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
