You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-issues@hadoop.apache.org by "Tsz-wo Sze (Jira)" <ji...@apache.org> on 2022/10/15 05:14:00 UTC

[jira] [Updated] (HADOOP-10416) For pseudo authentication, what to do if there is an expired token?

     [ https://issues.apache.org/jira/browse/HADOOP-10416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tsz-wo Sze updated HADOOP-10416:
--------------------------------
    Resolution: Not A Problem
        Status: Resolved  (was: Patch Available)

> 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 Sze
>            Assignee: Tsz-wo Sze
>            Priority: Minor
>              Labels: BB2015-05-TBR
>         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
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org