fix: use correct content type for token request #308
Merged
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
Updates the remaining SDKs to use the correct content type when making a token request.
FormUrlEncodedContent
as the body and then the runtime will handle setting theContent-Type
for usoauth2
package we includedpost_params
instead of bodyThis has been verified by running all 4 examples and providing credentials, where possible tests have been amended to assert we're passing the right header/body.
References
Closes #284
Language PRs to follow
Review Checklist
main