-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OAuth2 client credentials are sent with wrong Content-Type #47
Comments
Thanks for the report @nverbos-godaddy! |
@le-yams just looping you in as you had contributed that code. Would changing the content type still work for you? |
Absolutely, @nverbos-godaddy is right 😄 |
@rhamzeh I've created a PR in the sdk-generator project to fix this. |
Thank you! |
Thanks for the report @nverbos-godaddy and for your help @le-yams ! This should be out in the just released v0.3.2 |
Description
When an OAuth2 access token is requested from an OAuth2 Authorization server's token endpoint, the credentials are sent using the
application/json
Content-Type, but client credentials should be sent using theapplication/x-www-form-urlencoded
according to the OAuth 2.0 RFCVersion of SDK
v0.3.1
Reproduction
application/json
Expected behavior
When an OAuth2 token is requested from an OAuth2 Authorization server, the credentials are sent using the
application/x-www-form-urlencoded
content-type as specified in the OAuth 2.0 RFCThe text was updated successfully, but these errors were encountered: