Preserve current session when invalidating tokens [2.x] #3103
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
Fix User model to preserve the current session (provided via "options.accessToken") when invalidating access tokens after a change of email or password property.
bajtos
force-pushed
the
backport/preserve-current-access-token
branch
from
02a5e01 to
afd6dd7
Compare
doublemarked
approved these changes
Jan 16, 2017
|
@slnode test please |
1 similar comment
|
@slnode test please |
|
Released in |
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.
Back-port of #3098
See #3034
Important: the current session is preserved only when the User model has
injectOptionsFromRemoteContextenabled or the application injects the "options" argument using a custom solution.cc @ivanschwarz @doublemarked