Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Thu, 17 Mar 2016 12:26:33 +0000 (UTC)
From: "Larry McCay (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <JIRA.12951004.1458163455000.47729.1458217593783@Atlassian.JIRA>
In-Reply-To: <JIRA.12951004.1458163455000@Atlassian.JIRA>
References: <JIRA.12951004.1458163455000@Atlassian.JIRA>
 <JIRA.12951004.1458163455643@arcas>
Subject: [jira] [Updated] (HADOOP-12929) JWTRedirectAuthenticationHandler
 must accommodate null expiration time
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Larry McCay updated HADOOP-12929:
---------------------------------
    Status: Patch Available  (was: Open)

> JWTRedirectAuthenticationHandler must accommodate null expiration time
> ----------------------------------------------------------------------
>
>                 Key: HADOOP-12929
>                 URL: https://issues.apache.org/jira/browse/HADOOP-12929
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: security
>            Reporter: Larry McCay
>            Assignee: Larry McCay
>         Attachments: HADOOP-12929-001.patch, HADOOP-12929-002.patch
>
>
> The underlying JWT token within the hadoop-jwt cookie should be able to have no expiration time. This allows the token lifecycle to be the same as the cookie that contains it.
> Current validation processing of the token interprets the absence of an expiration time as requiring a new token to be acquired. JWT itself considers the exp to be an optional claim. As such, this patch will change the processing to accept a null expiration as valid for as long as the cookie is presented.


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