[
https://issues.apache.org/jira/browse/HADOOP-10307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benoy Antony updated HADOOP-10307:
----------------------------------
Attachment: HADOOP-10307.patch
Taking a different approach for this feature.
_CompositeAuthenticationHandler_ is added.
* _CompositeAuthenticationHandler_ accepts multiple _AuthenticationHandler_
via configuration.
* When processing an authentication request, it picks up the
_AuthenticationHandler_ based on url parameter “authtype”.
* If “authtype” is not specified, it uses the default
_AuthenticationHandler_(first one in the configured list of Authentication
Handlers).
* For no-Browser access, there can be a separate _AuthenticationHandler_. This
logic is borrowed from _AltKerberosAuthenticationHandler_.
*Note 1*: _CompositeAuthenticationHandler_ offers the features of
AltKerberosAuthenticationHandler. In addition, it allows configuring any number
of AuthenticationHandlers. Based on the parameters and header values, it
delegates control to the appropriate AuthenticationHandler.
*Note 2*: _AnonymousAuthenticationHandler_ is added. With this handler,
Anonymous access is achieved via a fixed account. Once can restrict the
anonymous access privileges by restricting the permissions of the anonymous
account.
> 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, 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.2#6252)
