Handling browser sessions in redis #1553
Closed
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.
This update allows managing browser sessions even when using Redis for session storage. It doesn't change existing functionality but adds new capabilities.
Moreover, it works correctly with the remember_me flag by ending all sessions on other devices except the current one.
The principle is simple: sessions are stored as usual, but we also save session IDs and other parameters in Redis for every user. This allows us to quickly find and end all active user sessions if needed.
The benefit of this update is confirmed by numerous requests for this improvement
#350
#1270