hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Haohui Mai (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 23:25:34 GMT

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

Haohui Mai commented on HADOOP-10416:
-------------------------------------

Just checked the code, I think that the current behavior has reasonable semantic.

The {{AuthenticationFilter}} sets the expiration time of the HTTP cookie the same as the expiration
time of the token. The client should reinitiate the authentication process once it founds
its HTTP cookie is expired.

> 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)

Mime
View raw message