Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Wed, 18 Feb 2015 18:18:12 +0000 (UTC)
From: "Benoy Antony (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <JIRA.12773614.1423524469000.77701.1424283492057@Atlassian.JIRA>
In-Reply-To: <JIRA.12773614.1423524469000@Atlassian.JIRA>
References: <JIRA.12773614.1423524469000@Atlassian.JIRA>
 <JIRA.12773614.1423524469262@arcas>
Subject: [jira] [Updated] (HADOOP-11567) Refresh HTTP Authentication secret
 without restarting the server
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Benoy Antony updated HADOOP-11567:
----------------------------------
    Attachment: HADOOP-11567-001.patch

Attaching the patch with testcases.

> 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
>         Attachments: HADOOP-11567-001.patch
>
>
> 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 secret.
> 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
(v6.3.4#6332)