[
https://issues.apache.org/jira/browse/KNOX-3120?focusedWorklogId=965579&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-965579
]
ASF GitHub Bot logged work on KNOX-3120:
----------------------------------------
Author: ASF GitHub Bot
Created on: 10/Apr/25 13:17
Start Date: 10/Apr/25 13:17
Worklog Time Spent: 10m
Work Description: lmccay merged PR #1019:
URL: https://github.com/apache/knox/pull/1019
Issue Time Tracking
-------------------
Worklog Id: (was: 965579)
Time Spent: 20m (was: 10m)
> Add a specialized use API for API KEY based on KNOXTOKEN API
> ------------------------------------------------------------
>
> Key: KNOX-3120
> URL: https://issues.apache.org/jira/browse/KNOX-3120
> Project: Apache Knox
> Issue Type: Improvement
> Components: Server
> Reporter: Larry McCay
> Assignee: Larry McCay
> Priority: Major
> Fix For: 2.2.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Similar to KNOX-3112 which added an API for CLIENTID for acquiring client
> credentials flow CLIENT_ID and CLIENT_SECRET we should add a specialized
> extension of KNOXTOKEN for an APIKEY API.
> The intent here is to add an API that both frees up KNOXTOKEN to be deployed
> within the same topology for known token exchange patterns as well as to
> codify the conventions that are being used by some that are using the
> passcode token as an API Key.
> We will make appropriate configuration and metadata defaults within the API
> implementation to reduce operations and config requirements and to return a
> translated response with the passcode as an {api_key: xxxx} or some similar
> response that meets standard or defacto standard expectations.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
