Added documentation for save_access_token, temporary credentials must not be reused. #202
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
…dentials should not be reused.
|
Excellent. I think we should take it one step further and add a specific method for this similar to invalidate_authorization_code that is invoked before returning the access token. |
|
@ib-lundgren I agree - it becomes more explicit and wouldn't make save_access_token do more than its name suggests. |
swistakm
added a commit
to swistakm/oauthlib
that referenced
this pull request
May 22, 2014
- add link to Section 2.3 RFC 5849 that explains why there is a need for token invalidation and give a clue how it can be invalidated (refs oauthlib#202) - add example implementation of validate_realms - explain why `verify_request_token` does not double functionality of `validate_request_token` (refs oauthlib#185)
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.
RFC 5849 section-2.3