[
https://issues.apache.org/jira/browse/KNOX-1022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16153130#comment-16153130
]
J.Andreina commented on KNOX-1022:
----------------------------------
when ttl is configured to higher value or to a negative value which when used
to calculate expiry and gives a value less than current time, then we can print
a log message that the value configured is invalid and use the default value
for ttl ( to be in sync with existing way to handle invalid values).
Will soon be providing a patch for the same
> 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
> Priority: Minor
>
> 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)
