[
https://issues.apache.org/jira/browse/HADOOP-15518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Minder updated HADOOP-15518:
----------------------------------
Description:
The hadoop-auth AuthenticationFilter will invoke its handler even if a prior
successful authentication has occurred. This primarily affects situations
where multipole authentication mechanism has been configured. For example when
core-site.xml's has hadoop.http.authentication.type and yarn-site.xml has
yarn.timeline-service.http-authentication.type the result is an attempt to
perform two Kerberos authentications for the same request. This in turn
results in Kerberos triggering a replay attack detection. The javadocs for
AuthenticationHandler
([https://github.com/apache/hadoop/blob/trunk/hadoop-common-project/hadoop-auth/src/main/java/org/apache/hadoop/security/authentication/server/AuthenticationHandler.java)]
indicate for the authenticate method that
{quote}This method is invoked by the AuthenticationFilter only if the HTTP
client request is not yet authenticated.
{quote}
This does not appear to be the cause in practice.
was:The hadoop-auth AuthenticationFilter will invoke its handler even if a
prior successful authentication has occurred. This primarily affects
situations where multipole authentication mechanism has been configured. For
example when core-site.xml's has hadoop.http.authentication.type and
yarn-site.xml has yarn.timeline-service.http-authentication.type the result is
an attempt to perform two Kerberos authentications for the same request. This
in turn results in Kerberos triggering a replay attack detection.
> Authentication filter calling handler after request already authenticated
> -------------------------------------------------------------------------
>
> Key: HADOOP-15518
> URL: https://issues.apache.org/jira/browse/HADOOP-15518
> Project: Hadoop Common
> Issue Type: Bug
> Components: security
> Affects Versions: 2.7.1
> Reporter: Kevin Minder
> Priority: Major
>
> The hadoop-auth AuthenticationFilter will invoke its handler even if a prior
> successful authentication has occurred. This primarily affects situations
> where multipole authentication mechanism has been configured. For example
> when core-site.xml's has hadoop.http.authentication.type and yarn-site.xml
> has yarn.timeline-service.http-authentication.type the result is an attempt
> to perform two Kerberos authentications for the same request. This in turn
> results in Kerberos triggering a replay attack detection. The javadocs for
> AuthenticationHandler
> ([https://github.com/apache/hadoop/blob/trunk/hadoop-common-project/hadoop-auth/src/main/java/org/apache/hadoop/security/authentication/server/AuthenticationHandler.java)]
> indicate for the authenticate method that
> {quote}This method is invoked by the AuthenticationFilter only if the HTTP
> client request is not yet authenticated.
> {quote}
> This does not appear to be the cause in practice.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
