[
https://issues.apache.org/jira/browse/KNOX-3142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandor Molnar updated KNOX-3142:
--------------------------------
Fix Version/s: 3.0.0
(was: 2.2.0)
Due to the pending 2.1.0 release this JIRA has been pushed out to 3.0.0 as part
of a bulk update. If there is a specific reason to pull this back into the
2.1.0 release and you intend to provide a PR in the next few days please
provide justification and reset the Fix Version to 2.1.0.
> Add support for client credentials flow to use HTTP Basic
> ---------------------------------------------------------
>
> Key: KNOX-3142
> URL: https://issues.apache.org/jira/browse/KNOX-3142
> Project: Apache Knox
> Issue Type: Improvement
> Components: Server
> Reporter: Larry McCay
> Assignee: Larry McCay
> Priority: Major
> Fix For: 3.0.0
>
>
> We currently expect client_id and client_secret for OAuth client credentials
> flow to be provided as part of the request body.
> It turns out that they are often and sometimes by default provided as HTTP
> Basic credentials by OIDC clients such as the quarkus.oidc-client extension.
> The JWTProvider which is where we support these credentials currently only
> supports Passcode and Token as the username and the respective token as the
> password.
> We need to open this up to client credentials flow by checking if it isn't
> one of those two that the grant_type=client_credentials is provided in the
> request body.
> At this time, we are able to configure that specific client to use a "post"
> method which puts them in the request body as we expect but we should close
> this gap.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
