[
https://issues.apache.org/jira/browse/KNOX-3119?focusedWorklogId=964937&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-964937
]
ASF GitHub Bot logged work on KNOX-3119:
----------------------------------------
Author: ASF GitHub Bot
Created on: 06/Apr/25 22:01
Start Date: 06/Apr/25 22:01
Worklog Time Spent: 10m
Work Description: lmccay opened a new pull request, #1016:
URL: https://github.com/apache/knox/pull/1016
Provide appropriate defaults for CLIENTID extension of KNOXTOKEN API
## What changes were proposed in this pull request?
There are a number of params that should be set by default for the CLIENTID
extension of the KNOXTOKEN API. This will reduce the likelihood of errors based
on having to explicitly configure these params which are either required or the
logical defaults.
1. knox.token.exp.server-managed should be enabled by default this service
if based on passcode tokens and requires server state
2. knox.token.ttl - should be -1 by default to not expire - fight me!
3. knox.token.hash.key should be set by default as well. We need to check
whether this already exists via the AliasService and if not we should generate
it automatically or fail to deploy with appropriate error/exception.
This required the creation of a hook into the KNOXTOKEN resource to allow
extensions to wrap the servletContext in order to provide defaults appropriate
to the extension that would otherwise require the deploying admin to configure
the same properties as convention for every deployment.
## How was this patch tested?
New unit tests added and existing tests run.
Manually tested.
Issue Time Tracking
-------------------
Worklog Id: (was: 964937)
Remaining Estimate: 0h
Time Spent: 10m
> Tune defaults for config params in CLIENTID API
> -----------------------------------------------
>
> Key: KNOX-3119
> URL: https://issues.apache.org/jira/browse/KNOX-3119
> Project: Apache Knox
> Issue Type: Improvement
> Components: Server
> Reporter: Larry McCay
> Assignee: Larry McCay
> Priority: Major
> Fix For: 2.2.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> There are a number of params that should be set by default for the CLIENTID
> extension of the KNOXTOKEN API. This will reduce the likelihood of errors
> based on having to explicitly configure these params which are either
> required or the logical defaults.
> 1. knox.token.exp.server-managed should be enabled by default this service if
> based on passcode tokens and requires server state
> 2. knox.token.ttl - should be -1 by default to not expire - fight me! :)
> 3. knox.token.hash.key should be set by default as well. We need to check
> whether this already exists via the AliasService and if not we should
> generate it automatically or fail to deploy with appropriate error/exception.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
