[ https://issues.apache.org/jira/browse/HADOOP-6995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928483#action_12928483 ] 

Hadoop QA commented on HADOOP-6995:
-----------------------------------

-1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12456673/hadoop-6995.txt
  against trunk revision 1031422.

    +1 @author.  The patch does not contain any @author tags.

    +1 tests included.  The patch appears to include 2 new or modified tests.

    +1 javadoc.  The javadoc tool did not generate any warning messages.

    +1 javac.  The applied patch does not increase the total number of javac compiler warnings.

    +1 findbugs.  The patch does not introduce any new Findbugs warnings.

    +1 release audit.  The applied patch does not increase the total number of release audit warnings.

    -1 core tests.  The patch failed core unit tests.

    +1 contrib tests.  The patch passed contrib unit tests.

    +1 system test framework.  The patch passed system test framework compile.

Test results: https://hudson.apache.org/hudson/job/PreCommit-HADOOP-Build/13//testReport/
Findbugs warnings: https://hudson.apache.org/hudson/job/PreCommit-HADOOP-Build/13//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output: https://hudson.apache.org/hudson/job/PreCommit-HADOOP-Build/13//console

This message is automatically generated.

> Allow wildcards to be used in ProxyUsers configurations
> -------------------------------------------------------
>
>                 Key: HADOOP-6995
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6995
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: security
>    Affects Versions: 0.22.0
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>            Priority: Minor
>         Attachments: hadoop-6995-branch20.txt, hadoop-6995.txt
>
>
> There are some cases where the full tightness of the ProxyUsers configuration is not required or available -- for example, not all users of oozie may share a common "oozie-users" group, and the operators would prefer to allow oozie on a given host to act proxy for any user. We should allow the operator to specify a wildcard for hosts or groups in the proxyuser configurations.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.