Don't pass the request headers to 3scale backend for native OAuth flow #433
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
mayorova
changed the title
mayorova
force-pushed
the
fix-oauth-store-headers
branch
2 times, most recently
from
5d7bb6d to
b21806a
Compare
mikz
approved these changes
Sep 29, 2017
mayorova
force-pushed
the
fix-oauth-store-headers
branch
from
b21806a to
772c46d
Compare
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.
Keeping the request headers may be causing the issue with passing an incorrect
Content-Typeto the 3scale backend when storing the access token (POST https://su1.3scale.net/services/<SERVICE_ID>/oauth_access_tokens.xml).The only valid content types for this endpoint are:
application/x-www-form-urlencodedapplication/x-www-form-urlencodedimplicitly)