You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@knox.apache.org by "Sandor Molnar (Jira)" <ji...@apache.org> on 2026/07/30 05:35:00 UTC

[jira] [Updated] (KNOX-3401) Switch OOTB JDBC-based token state service from Derby to something else

     [ https://issues.apache.org/jira/browse/KNOX-3401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sandor Molnar updated KNOX-3401:
--------------------------------
    Attachment: image-2026-07-30-07-34-16-369.png

> Switch OOTB JDBC-based token state service from Derby to something else
> -----------------------------------------------------------------------
>
>                 Key: KNOX-3401
>                 URL: https://issues.apache.org/jira/browse/KNOX-3401
>             Project: Apache Knox
>          Issue Type: Bug
>    Affects Versions: 3.0.0
>            Reporter: Sandor Molnar
>            Priority: Major
>         Attachments: image-2026-07-30-07-34-16-369.png
>
>
> The community agreed to switch from alias-based TSS to JDBC-based TSS as the default implementation due to several reasons, details are found in [this e-mail thread|https://lists.apache.org/thread/fs9nkl6l45o330ttvgvqxj3jnxt63bcs].
> At that time (late 2023), Derby DB seemed a good choice given its wide range of configs and community support. However, the project os now retired, this is what's listed on their Apache page:
> h2. Derby Retired
> *On 2025-10-10, the Derby developers voted to retire the project into a read-only state. Derby development and bug-fixing have ended. No further releases will be published. The Derby website and wiki are frozen in place. Derby JIRA issues are now read-only and new bugs cannot be logged. The user and developer lists are disabled and can be accessed only through their archives.*
>  
> Therefore, we need to find another DB vendor that satisfies our needs and can be used as Knox's default token state backend.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)