Mailing-List: contact common-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-dev@hadoop.apache.org
Date: Mon, 9 Feb 2015 23:28:35 +0000 (UTC)
From: "Benoy Antony (JIRA)" <jira@apache.org>
To: common-dev@hadoop.apache.org
Message-ID: <JIRA.12773614.1423524469000.305862.1423524515674@Atlassian.JIRA>
In-Reply-To: <JIRA.12773614.1423524469000@Atlassian.JIRA>
References: <JIRA.12773614.1423524469000@Atlassian.JIRA>
 <JIRA.12773614.1423524469262@arcas>
Subject: [jira] [Created] (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

Benoy Antony created HADOOP-11567:
-------------------------------------

             Summary: 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 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)