hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benoy Antony (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-11567) Refresh HTTP Authentication secret without restarting the server
Date Mon, 09 Feb 2015 23:38:35 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-11567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14313170#comment-14313170

Benoy Antony commented on HADOOP-11567:


_FileSignerSecretProvider_ will provide the secret based on the contents of the file.

h5.At Init 

Uses _FileSignerSecretProvider_ and obtains the secret.

h5. update

Use _WatcherService_ to identify the file change , loads the new secret and starts using the
new secret.

h5. Options: 

Effective time in milliseconds : time at which the secret will be used to sign and verify
, defaults to 0, which means immediately
Transition period in seconds : during which old secrets are valid, defaults to 0.

h5.Property file format

> Refresh HTTP Authentication secret without restarting the server
> ----------------------------------------------------------------
>                 Key: HADOOP-11567
>                 URL: https://issues.apache.org/jira/browse/HADOOP-11567
>             Project: Hadoop Common
>          Issue Type: Improvement
>    Affects Versions: 2.6.0
>            Reporter: Benoy Antony
>            Assignee: Benoy Antony
> The _AuthenticationFilter_ uses the secret read from a file specified via hadoop.http.authentication.signature.secret.file
to sign the cookie containing user authentication information.
> The secret is read only during initialization and hence needs a restart to update the
> ZKSignerSecretProvider can be used to rotate the secrets without restarting the servers,
but it needs a zookeeper setup.
> The jira is to refresh secret by updating the file.

This message was sent by Atlassian JIRA

View raw message