[
https://issues.apache.org/jira/browse/KNOX-3112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandeep More updated KNOX-3112:
-------------------------------
Fix Version/s: 2.1.0
(was: 2.2.0)
> 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.1.0
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> 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)
