[
https://issues.apache.org/jira/browse/KNOX-2597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17338579#comment-17338579
]
ASF subversion and git services commented on KNOX-2597:
-------------------------------------------------------
Commit b7e4075939772b98e67ee34a37fb3c2129a7bdf0 in knox's branch
refs/heads/master from Sandor Molnar
[ https://gitbox.apache.org/repos/asf?p=knox.git;h=b7e4075 ]
KNOX-2597 - Falling back to AliasBasedTokenStateService in case of DB
configuration issues (#441)
Additionally, we display informative status messages on the tokengen
application UI about the configured token management backend.
> 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
> 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)
