[
https://issues.apache.org/jira/browse/HADOOP-12082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14698056#comment-14698056
]
Larry McCay commented on HADOOP-12082:
--------------------------------------
Hi [~hgadre] - Thank you for reaching out - I look forward to reviewing it!
I will try and carve out some time this weekend to take a look at the patch in
detail.
The service loader pluggability that I mentioned before would be a Java
ServiceLoader mechanism to load a set of classes that implement a given
interface. If you provide a getName() as part of that interface then you can
iterate over the set to pull out the specific configured handler.
What I am trying to do is provide a decoupling of the challenge type and the
actual backend authentication type.
So, if we could indicate that HTTP Basic auth was accepted through the
challenge, we could have the backend authenticate against the preferred user
store: LDAP, RDBMS, etc. Rather than tying HTTP Basic auth the LDAP alone.
The easiest way forward - I think - is to provide an implementation with
discrete handlers for the challenges. We can then refactor that to support
multiple backends.
I would get your concrete usecases met with an implementation that we can move
forward and maintain backward compatibility for without slowing progress.
Adding pluggability later shouldn't be too hard and having tests for the
initial functionality would help that work.
> Support multiple authentication schemes via AuthenticationFilter
> ----------------------------------------------------------------
>
> Key: HADOOP-12082
> URL: https://issues.apache.org/jira/browse/HADOOP-12082
> Project: Hadoop Common
> Issue Type: Improvement
> Components: security
> Affects Versions: 2.6.0
> Reporter: Hrishikesh Gadre
> Assignee: Hrishikesh Gadre
> Attachments: hadoop-ldap.patch, multi-scheme-auth-support-poc.patch
>
>
> The requirement is to support LDAP based authentication scheme via Hadoop
> AuthenticationFilter. HADOOP-9054 added a support to plug-in custom
> authentication scheme (in addition to Kerberos) via
> AltKerberosAuthenticationHandler class. But it is based on selecting the
> authentication mechanism based on User-Agent HTTP header which does not
> conform to HTTP protocol semantics.
> As per [RFC-2616|http://www.w3.org/Protocols/rfc2616/rfc2616.html]
> - HTTP protocol provides a simple challenge-response authentication mechanism
> that can be used by a server to challenge a client request and by a client to
> provide the necessary authentication information.
> - This mechanism is initiated by server sending the 401 (Authenticate)
> response with ‘WWW-Authenticate’ header which includes at least one challenge
> that indicates the authentication scheme(s) and parameters applicable to the
> Request-URI.
> - In case server supports multiple authentication schemes, it may return
> multiple challenges with a 401 (Authenticate) response, and each challenge
> may use a different auth-scheme.
> - A user agent MUST choose to use the strongest auth-scheme it understands
> and request credentials from the user based upon that challenge.
> The existing Hadoop authentication filter implementation supports Kerberos
> authentication scheme and uses ‘Negotiate’ as the challenge as part of
> ‘WWW-Authenticate’ response header. As per the following documentation,
> ‘Negotiate’ challenge scheme is only applicable to Kerberos (and Windows
> NTLM) authentication schemes.
> [SPNEGO-based Kerberos and NTLM HTTP
> Authentication|http://tools.ietf.org/html/rfc4559]
> [Understanding HTTP
> Authentication|https://msdn.microsoft.com/en-us/library/ms789031%28v=vs.110%29.aspx]
> On the other hand for LDAP authentication, typically ‘Basic’ authentication
> scheme is used (Note TLS is mandatory with Basic authentication scheme).
> http://httpd.apache.org/docs/trunk/mod/mod_authnz_ldap.html
> Hence for this feature, the idea would be to provide a custom implementation
> of Hadoop AuthenticationHandler and Authenticator interfaces which would
> support both schemes - Kerberos (via Negotiate auth challenge) and LDAP (via
> Basic auth challenge). During the authentication phase, it would send both
> the challenges and let client pick the appropriate one. If client responds
> with an ‘Authorization’ header tagged with ‘Negotiate’ - it will use Kerberos
> authentication. If client responds with an ‘Authorization’ header tagged with
> ‘Basic’ - it will use LDAP authentication.
> Note - some HTTP clients (e.g. curl or Apache Http Java client) need to be
> configured to use one scheme over the other e.g.
> - curl tool supports option to use either Kerberos (via --negotiate flag) or
> username/password based authentication (via --basic and -u flags).
> - Apache HttpClient library can be configured to use specific authentication
> scheme.
> http://hc.apache.org/httpcomponents-client-ga/tutorial/html/authentication.html
> Typically web browsers automatically choose an authentication scheme based on
> a notion of “strength” of security. e.g. take a look at the [design of Chrome
> browser for HTTP
> authentication|https://www.chromium.org/developers/design-documents/http-authentication]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
