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 2021/05/03 19:36:00 UTC
[jira] [Updated] (KNOX-2597) Fallback to
AliasBasedTokenStateService in case of DB errors
[ https://issues.apache.org/jira/browse/KNOX-2597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sandor Molnar updated KNOX-2597:
--------------------------------
Fix Version/s: 1.6.0
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Fallback to AliasBasedTokenStateService in case of DB errors
> ------------------------------------------------------------
>
> Key: KNOX-2597
> URL: https://issues.apache.org/jira/browse/KNOX-2597
> Project: Apache Knox
> Issue Type: Task
> Affects Versions: 1.6.0
> Reporter: Sandor Molnar
> Assignee: Sandor Molnar
> Priority: Major
> Fix For: 1.6.0
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> We recently added support to pure JDBC-based token state management. It'd be great to make deployments smooth with the following safety net: if there is (are) any issue(s) with the configured DB connection, the Knox Gateway should start using the {{AliasBasedTokenStateService}} instead of fail-fast. Additionally, the {{tokengen}} UI should indicate the fact if the underlying token back-end is the one the user configured.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)