[
https://issues.apache.org/jira/browse/KNOX-3075?focusedWorklogId=945683&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-945683
]
ASF GitHub Bot logged work on KNOX-3075:
----------------------------------------
Author: ASF GitHub Bot
Created on: 26/Nov/24 10:11
Start Date: 26/Nov/24 10:11
Worklog Time Spent: 10m
Work Description: smolnar82 merged PR #970:
URL: https://github.com/apache/knox/pull/970
Issue Time Tracking
-------------------
Worklog Id: (was: 945683)
Time Spent: 0.5h (was: 20m)
> JDBC Token State Server not handling -1 Expiry Correctly
> --------------------------------------------------------
>
> Key: KNOX-3075
> URL: https://issues.apache.org/jira/browse/KNOX-3075
> Project: Apache Knox
> Issue Type: Bug
> Components: JWT
> Reporter: Larry McCay
> Assignee: Sandor Molnar
> Priority: Major
> Fix For: 2.1.0
>
> Attachments: image-2024-11-16-12-02-03-545.png,
> image-2024-11-16-12-02-34-329.png
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> With server managed state for JWT and passcode tokens and the token state
> server set to JDBC/Derby, a -1 expiration results in an UnknownTokenException
> inappropriately.
> !image-2024-11-16-12-02-03-545.png!
> The above image shows tokens with Never as the expiration.
> !image-2024-11-16-12-02-34-329.png!
> The next image shows that an expiration of -1 will result in the
> UnknownTokenException.
> Changing back to the Alias based token state server resolved this issue.
> Since this is no longer the default TSS, we are broken out of the box.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
