[V2] Officially support authenticated sessions and allow to perform certain actions on them. #780
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.
Issue
Resolves #510.
Resolves #778.
Resolves #779.
Solution and steps
Session
constructor for better readability.userId
toSession
.Session.userId
when saving and reading the session (and updating from redis).@TokenRequired
useSession.userId
to authenticate the session.TypeORMStore.getAuthenticatedUserIds()
TypeORMStore.destroyAllSessionsOf(user)
TypeORMStore.getSessionsOf(user)
Breaking changes
Session
constructor.TypeORMStore
only support numbers (not strings) as user IDs.userId
is not stored in the session content.sessions:
instead ofsession:
.sessions
instead offoalSessions
.When migrating to v2, all users will be logged out.
When migrating to v2 (optional) :
foalSessions
collection.Checklist