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

Hadoop QA commented on HADOOP-10416:
------------------------------------

\\
\\
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:red}-1{color} | patch |   0m  0s | The patch command could not apply 
the patch during dryrun. |
\\
\\
|| Subsystem || Report/Notes ||
| Patch URL | 
http://issues.apache.org/jira/secure/attachment/12636205/c10416_20140322.patch |
| Optional Tests | javadoc javac unit findbugs checkstyle |
| git revision | trunk / f1a152c |
| Console output | 
https://builds.apache.org/job/PreCommit-HADOOP-Build/6371/console |


This message was automatically generated.

> For pseudo authentication, what to do if there is an expired token?
> -------------------------------------------------------------------
>
>                 Key: HADOOP-10416
>                 URL: https://issues.apache.org/jira/browse/HADOOP-10416
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: security
>            Reporter: Tsz Wo Nicholas Sze
>            Assignee: Tsz Wo Nicholas Sze
>            Priority: Minor
>         Attachments: c10416_20140321.patch, c10416_20140322.patch
>
>
> PseudoAuthenticationHandler currently only gets username from the "user.name" 
> parameter.  If there is an expired auth token in the request, the token is 
> ignored (without returning any error back to the client).  Further, if 
> anonymous is enabled, the client will be authenticated as anonymous.
> The above behavior seems non-desirable since the client does not want to be 
> authenticated as anonymous.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to