You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@knox.apache.org by "Larry McCay (Jira)" <ji...@apache.org> on 2025/03/25 23:39:00 UTC

[jira] [Updated] (KNOX-3112) Add a specialized use API for CLIENT_ID and SECRET based on KNOXTOKEN API

     [ https://issues.apache.org/jira/browse/KNOX-3112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Larry McCay updated KNOX-3112:
------------------------------
    Summary: Add a specialized use API for CLIENT_ID and SECRET based on KNOXTOKEN API  (was: Add a specialized use API for CLIENT_ID and SECRET base don KNOXTOKEN API)

> Add a specialized use API for CLIENT_ID and SECRET based on KNOXTOKEN API
> -------------------------------------------------------------------------
>
>                 Key: KNOX-3112
>                 URL: https://issues.apache.org/jira/browse/KNOX-3112
>             Project: Apache Knox
>          Issue Type: Improvement
>          Components: Server
>            Reporter: Larry McCay
>            Assignee: Larry McCay
>            Priority: Major
>             Fix For: 2.2.0
>
>
> Given the ability to support the OAuth client credentials flow with a specialized use of the tokenid and passcode token from the KNOXTOKEN API, we should add a corresponding API for acquiring the CLIENT_ID and CLIENT_SECRET without requiring consumers to understand this specialized use. We will codify the conventions being used for that into the new API extension of KNOXTOKEN which will make CLIENTID's first class concepts rather than an interpretation of KNOXTOKEN API responses.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)