hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arun Suresh (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-11187) NameNode - KMS communication fails after a long period of inactivity
Date Tue, 04 Nov 2014 10:10:34 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-11187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Arun Suresh updated HADOOP-11187:
    Attachment: HADOOP-11187.1.patch

Uploading initial patch

* {{KMSClientProvider}} now retries 403 responses with Invalid Signature
* If the AuthenticationFIlter 401 responses do not contain a 'WWW-Authenticate' header, send
a 403 (Since a 401 is required to have a 'WWW-Authenticate' method)
* Fixed up test-cases
* The {{PseudoAuthenticationHandler}} now does not throw an exception if {{user.name}} is
not found.. it returns a null token which will be returned to client as 401

> NameNode - KMS communication fails after a long period of inactivity
> --------------------------------------------------------------------
>                 Key: HADOOP-11187
>                 URL: https://issues.apache.org/jira/browse/HADOOP-11187
>             Project: Hadoop Common
>          Issue Type: Bug
>    Affects Versions: 2.6.0
>            Reporter: Arun Suresh
>            Assignee: Arun Suresh
>         Attachments: HADOOP-11187.1.patch
> As reported by [~atm] :
> The issue is due to the authentication token that the NN has to talk to the KMS is expiring,
AND the signature secret provider in the KMS authentication filter is discarding the old secret
after 2x the authentication token validity period.
> If the token being supplied is under 1x the validity lifetime then the token will authenticate
just fine. If the token being supplied is between 1x-2x the validity lifetime, then the token
can be validated but it will be expired, so a 401 will be returned to the client and it will
get a new token. But if the token being supplied is greater than 2x the validity lifetime,
then the KMS authentication filter will not even be able to validate the token, and will return
a 403, which will cause the client to not retry authentication to the KMS.
> The KMSClientProvider needs to be modified to retry authentication even in the above

This message was sent by Atlassian JIRA

View raw message