You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@knox.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2025/07/09 09:23:00 UTC
[jira] [Commented] (KNOX-3155) Isolate the CLIENTID and APIKEY param names from KNOXTOKEN
[ https://issues.apache.org/jira/browse/KNOX-3155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18004066#comment-18004066 ]
ASF subversion and git services commented on KNOX-3155:
-------------------------------------------------------
Commit 59951833ea768bf1023b34ab22c40ce3615de5af in knox's branch refs/heads/dependabot/npm_and_yarn/knox-token-generation-ui/multi-635efc449e from Larry McCay
[ https://gitbox.apache.org/repos/asf?p=knox.git;h=59951833e ]
KNOX-3155 - Isolate the CLIENTID and APIKEY param names from KNOXTOKEN (#1052)
* KNOX-3155 - Isolate the CLIENTID and APIKEY param names from KNOXTOKEN
> Isolate the CLIENTID and APIKEY param names from KNOXTOKEN
> ----------------------------------------------------------
>
> Key: KNOX-3155
> URL: https://issues.apache.org/jira/browse/KNOX-3155
> Project: Apache Knox
> Issue Type: Bug
> Components: Server
> Reporter: Larry McCay
> Assignee: Larry McCay
> Priority: Major
> Fix For: 2.1.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The new APIs that extend KNOXTOKEN API leverage the param names of the parent API even when it translates from one to the other. There is a problem with colocating any of these three APIs in the same topology as the params are getting confused across the implementations and they step on each other.
> We need to disambiguate them based on prefixes for the extensions that can be used in the init method and set the appropriate member variables in either the parent or the extension for use by the runtime.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)