[
https://issues.apache.org/jira/browse/HADOOP-6581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12869382#action_12869382
]
Hadoop QA commented on HADOOP-6581:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12444973/c6581-17.patch
against trunk revision 945953.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 3 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.
Test results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h4.grid.sp2.yahoo.net/532/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h4.grid.sp2.yahoo.net/532/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h4.grid.sp2.yahoo.net/532/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h4.grid.sp2.yahoo.net/532/console
This message is automatically generated.
> Add authenticated TokenIdentifiers to UGI so that they can be used for
> authorization
> ------------------------------------------------------------------------------------
>
> Key: HADOOP-6581
> URL: https://issues.apache.org/jira/browse/HADOOP-6581
> Project: Hadoop Common
> Issue Type: New Feature
> Components: ipc, security
> Reporter: Kan Zhang
> Assignee: Kan Zhang
> Attachments: c6581-10.patch, c6581-12.patch, c6581-13.patch,
> c6581-14.patch, c6581-15.patch, c6581-16.patch, c6581-17.patch
>
>
> When token is used for authentication over RPC, information other than
> username may be needed for access authorization. This information is
> typically specified in TokenIdentifier. This is especially true for block
> tokens used for client-to-datanode accesses, where authorization is based on
> access permissions specified in TokenIdentifier, and not on username. Block
> tokens used to be called access tokens and one can think of them as
> capability tokens. See HADOOP-4359 for more info.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
