Fix content-type in client_credentials oauth flow #2039
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Merged! Thank you @PushpenderSaini0 ! This will go out in the cc @lohit-1 |
slowjoe007
pushed a commit
to slowjoe007/bruno
that referenced
this pull request
Apr 10, 2024
Its-treason
pushed a commit
to Its-treason/bruno
that referenced
this pull request
Apr 13, 2024
2 tasks
lizziemac
pushed a commit
to lizziemac/bruno
that referenced
this pull request
May 4, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 was getting error while using the client credential oauth flow on
login.microsoftonline.comAs per RFC 6749 section-4.4 the client credential grant must have "application/x-www-form-urlencoded" format !
This PR adds the format as a header !
I have verified this fixes the issue 馃槃 !
Fixes #1987
Fixes #1976
Fixes #1938
Contribution Checklist: