[
https://issues.apache.org/jira/browse/KNOX-1022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16219335#comment-16219335
]
ASF subversion and git services commented on KNOX-1022:
-------------------------------------------------------
Commit aa62fa2dbdca59b175eefb62e97b5528f40d076b in knox's branch
refs/heads/KNOX-998-Package_Restructuring from [~coheigea]
[ https://git-wip-us.apache.org/repos/asf?p=knox.git;h=aa62fa2 ]
KNOX-1022 - Configuring knox token ttl to higher value generates an access
token which is not valid
> Configuring knox token ttl to higher value generates an access token which is
> not valid
> ---------------------------------------------------------------------------------------
>
> Key: KNOX-1022
> URL: https://issues.apache.org/jira/browse/KNOX-1022
> Project: Apache Knox
> Issue Type: Bug
> Components: Server
> Reporter: J.Andreina
> Assignee: Colm O hEigeartaigh
> Priority: Minor
> Fix For: 0.14.0
>
>
> If TTL for Knox token is configured to negative value other than -1 or
> configured to a value in milli seconds which when gets added to current time
> in milli seconds to calculate the token expiry becomes > LONG.MAX_VALUE, then
> token expiry will become negative value. In such cases there is no need to go
> ahead and generate a token which will not be valid at all (already expired).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
