hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-10416) For pseudo authentication, what to do if there is an expired token?
Date Fri, 03 Oct 2014 22:34:34 GMT

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

Hadoop QA commented on HADOOP-10416:

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  against trunk revision 7f6ed7f.

    {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:red}-1 javac{color:red}.  The patch appears to cause the build to fail.

Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/4859//console

This message is 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

View raw message