Add the ability to pass additional URL parameters to the authorize() call #74
Conversation
This file contains hidden or 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
flask_oauthlib/client.py
Outdated
|
merged at e6c5d75 |
|
Awesome, thanks @lepture! Are you planning on a release any time soon? |
|
@svvitale 0.4.3 is released. |
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.
Hello,
I've modified the authorize() call to allow for additional URL parameters that you may not want to include in the request_token_params instance variable. This allows you to have one OAuthRemoteApp instance that can be used with a variety of query parameters. For example, with Google OAuth, I'm able to pass prompt="none" for authentication only, and prompt="consent" when I want to prompt the user for access.
Please let me know if you have any questions about my use case or the changes themselves.
-Scott