[
https://issues.apache.org/jira/browse/KNOX-3075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17901155#comment-17901155
]
ASF subversion and git services commented on KNOX-3075:
-------------------------------------------------------
Commit 683c499b84d33bef1c4a95e5248bcbb358b29f4c in knox's branch
refs/heads/master from Sandor Molnar
[ https://gitbox.apache.org/repos/asf?p=knox.git;h=683c499b8 ]
KNOX-3075 - Handling unlimited token expiration in JDBC TSS properly (#970)
Co-authored-by: Sandor Molnar <sandor.mol...@iipay.com>
> 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)
