[
https://issues.apache.org/jira/browse/AMBARI-15479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15236130#comment-15236130
]
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/12798024/AMBARI-15479-002.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/6354//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, AMBARI-15479-002.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)
