This repository was archived by the owner on May 1, 2024. It is now read-only.
Add new property to disable the escaping of scope parameter. #62
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.
By default, the OAuth2Authenticator escapes the scope parameter. When multiple scopes are provided (example: "basic+comments+relationships+likes"), some OAuth2 providers (such as Instagram) return an HTTP 400 BAD REQUEST on authentication. This is because the encoding of the "+" character to "%2B" is not accepted by some OAuth2 providers (such as Instagram). This commit adds a property named DoNotEscapeScope that can be set to true to circumvent the issue.