[
https://issues.apache.org/jira/browse/KNOX-2828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandor Molnar updated KNOX-2828:
--------------------------------
+Apache Knox 3.0.0 release preparation+
We are about to cut the 3.0.0 release branch. master will move on to 3.1.0.
This issue is currently unresolved and is not automatically included in 3.0.0.
Please choose one of the following:
# If this belongs in 3.0.0: once the branch is cut, cherry-pick your commit(s)
onto the new v3.0.0 branch in addition to master. Leave Fix Version = 3.0.0 so
we can track it.
# Do nothing: we will move this issue to the next release (3.1.0) as part of
release cleanup.
If we don't hear back and see no cherry-pick, the issue will be re-targeted to
3.1.0. Thanks!
> Token generation maximum token ttl unlimited not working when lifespan input
> is disabled
> ----------------------------------------------------------------------------------------
>
> Key: KNOX-2828
> URL: https://issues.apache.org/jira/browse/KNOX-2828
> Project: Apache Knox
> Issue Type: Bug
> Components: Homepage, Server
> Reporter: Marton Balázs
> Priority: Minor
> Fix For: 3.0.0
>
>
> Even though there's no documentation about this feature, when the _KNOXTOKEN_
> service param _knox.token.ttl_ is set to _-1_ in the _homepage_ topology, the
> token generation site indicates that the generated token lifetime can be
> {_}unlimited{_}. Combining this with configuring the
> _knox.token.lifespan.input.enabled_ param of the _KNOXTOKEN_ service to
> _false_ and generating a token, result in generating a token which expiry
> date is: _01/01/1970, 00:59:59._
> Configurations for recreation of the problem:
> In homepage topology KNOXTOKEN service
> {code:java}
> <param>
> <name>knox.token.ttl</name>
> <value>-1</value>
> </param>
> <param>
> <name>knox.token.lifespan.input.enabled</name>
> <value>false</value>
> </param>
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
