Add support for multiple access tokens per user (#977) #982
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
…emoving code that deletes a user's extra refresh tokens.
|
Thanks for the patch! |
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.
Cleaned up and fixed the diff posted in #977.
This adds support for multiple access tokens per-user, a common use-case where a user might want to authenticate with Drupal from multiple devices (phone, tablet, 3rd party service, etc).
This modifies previous functionality of reusing existing access token / removing extra refresh tokens (which broke if you had two+ devices attempting to refresh with the same refresh token). An alternative would be to support both strategies and add configuration option to toggle between them.