Improvement: Add client credentials location parameter for Client Credentials OAuth flow #9730
+110
−83
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
I have developed a fix to make the user able to send OAuth client credentials (that is, client ID and secret) in the request body. The fix consists of an additional dropdown box to determine the
authActions
file flow.Motivation and Context
Fixes #9711
This change is needed by niche use cases, e.g. when the partner client does not fully comply to the Section 2.3.1 of RFC 6479 standard - sometimes due to requiring the client to send the client credentials in the JSON body content. This is experienced by me first-hand, as I have to develop an API to integrate with such example of a service.
How Has This Been Tested?
Manual quality assurance (QA).
Screenshots (if appropriate):
Checklist
My PR contains...
src/
is unmodified: changes to documentation, CI, metadata, etc.)package.json
)My changes...
Documentation
Automated tests