[
https://issues.apache.org/jira/browse/HADOOP-10416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14158606#comment-14158606
]
Jitendra Nath Pandey commented on HADOOP-10416:
-----------------------------------------------
I think it is a valid use case that same clients do not want to fallback to
anonymous user if the token is expired, even if the server is configured to
allow anonymous access.
One possible approach to allow that without breaking compatibility would be
to add an optional parameter in the request, where client can specify
'nonanonymous'. On receiving this, the server will not fallback to anonymous if
the token has expired, instead it will throw an exception.
Thoughts?
> 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)
