[
https://issues.apache.org/jira/browse/HADOOP-10307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13901925#comment-13901925
]
Benoy Antony commented on HADOOP-10307:
---------------------------------------
[~wheat9] I can take a stab applying the similar approach to webhdfs.
bq. I think it might be more appropriate to put the authType into the HTTP
header / cookie, since it can potentially conflicts with other web-based
applications.
Could you please explain the conflict created by the new parameter - authtype ?
The parameter - _authtype_ is used to the select authenticatonHandler. If
_authtype_ is not present, the default authenticationHandler is used. How will
it help if this information is passed in a cookie ?
> Support multiple Authentication mechanisms for HTTP
> ---------------------------------------------------
>
> Key: HADOOP-10307
> URL: https://issues.apache.org/jira/browse/HADOOP-10307
> Project: Hadoop Common
> Issue Type: Improvement
> Components: security
> Affects Versions: 2.2.0
> Reporter: Benoy Antony
> Assignee: Benoy Antony
> Attachments: HADOOP-10307.patch
>
>
> Currently it is possible to specify a custom Authentication Handler for HTTP
> authentication.
> We have a requirement to support multiple mechanisms to authenticate HTTP
> access.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
