Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Mon, 15 Jun 2015 22:05:01 +0000 (UTC)
From: "hzlu (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <JIRA.12834389.1433195136000.76978.1434405901183@Atlassian.JIRA>
In-Reply-To: <JIRA.12834389.1433195136000@Atlassian.JIRA>
References: <JIRA.12834389.1433195136000@Atlassian.JIRA>
 <JIRA.12834389.1433195136789@arcas>
Subject: [jira] [Updated] (HADOOP-12049) Control http authentication cookie
 persistence via configuration
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

hzlu updated HADOOP-12049:
--------------------------
    Status: Open  (was: Patch Available)

> Control http authentication cookie persistence via configuration
> ----------------------------------------------------------------
>
>                 Key: HADOOP-12049
>                 URL: https://issues.apache.org/jira/browse/HADOOP-12049
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: security
>    Affects Versions: 2.4.1
>            Reporter: Benoy Antony
>            Assignee: hzlu
>              Labels: patch
>             Fix For: 2.4.1
>
>         Attachments: 0001-Control-http-authentication-cookie-persistence.patch
>
>
> During http authentication, a cookie is dropped. This is a persistent cookie. The cookie is valid across browser sessions.
> For clusters which require enhanced security,  it is desirable to have a session cookie so that cookie gets deleted when the user closes browser session.
> It should be possible to specify cookie persistence (session or persistent) via configuration 


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)