[
https://issues.apache.org/jira/browse/KNOX-3187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandor Molnar updated KNOX-3187:
--------------------------------
Status: Patch Available (was: In Progress)
> Better indicator of missing knox.token.hash.key on Token
> Management/Generation UIs
> ----------------------------------------------------------------------------------
>
> Key: KNOX-3187
> URL: https://issues.apache.org/jira/browse/KNOX-3187
> Project: Apache Knox
> Issue Type: Improvement
> Affects Versions: 2.0.0, 2.1.0
> Reporter: Sandor Molnar
> Assignee: Sandor Molnar
> Priority: Blocker
> Fix For: 2.1.0
>
> Attachments: image-2025-09-09-08-41-30-504.png,
> image-2025-09-09-08-42-19-091.png
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> As of now, when there is no `knox.token.hash.key` alias stored in the
> gateway-level credential store and one hits the Token Management or Token
> Generation UI, the following pop-up windows are shown:
> !image-2025-09-09-08-41-30-504.png|height=200!
> !image-2025-09-09-08-42-19-091.png|height=200!
> The only way to find out what causes this issue is to check the logs, where
> the root cause is clearly indicated:
> {code}
> Caused by: org.glassfish.hk2.api.MultiException: A MultiException has 2
> exceptions. They are:
> 1. org.apache.knox.gateway.services.ServiceLifecycleException: Missing
> knox.token.hash.key alias from Gateway's credential store
> 2. java.lang.IllegalStateException: Unable to perform operation: post
> construct on org.apache.knox.gateway.service.knoxtoken.TokenResourceV2
> {code}
> To avoid this, we need to improve the error message within the popup window
> to tell the users they need this key before they can use the token management
> feature.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
