ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-15479) JwtAuthenticationFilter needs to accommodate null JWT expiration time
Date Sat, 19 Mar 2016 17:00:34 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-15479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15202850#comment-15202850
] 

Hadoop QA commented on AMBARI-15479:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12794183/AMBARI-15479-001.patch
  against trunk revision .

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/5936//console

This message is automatically generated.

> JwtAuthenticationFilter needs to accommodate null JWT expiration time
> ---------------------------------------------------------------------
>
>                 Key: AMBARI-15479
>                 URL: https://issues.apache.org/jira/browse/AMBARI-15479
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>            Reporter: Larry McCay
>            Assignee: Larry McCay
>         Attachments: AMBARI-15479-001.patch
>
>
> Current validation of the JWT token within the SSO cookie interprets no expiration date
as expired and redirects to acquire a new cookie. In the JWT specification exp is an optional
claim however. KnoxSSO is leveraging this to mean that the token lifecycle should be tied
to that of the SSO cookie itself and not timeout from underneath the cookie.
> This minor change will allow null expiration times within the JWT token to be considered
valid.



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

Mime
View raw message