feat: add server side session storage #265
Open
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 PR adds a server side storage option for sessions using
useStorage
.The default behavior after this PR is still the same as before (using cookie as storageType which is the default)
but now the storageType can be
memory
,cache
ornuxt-session
as well, wherenuxt-session
is a nitro storage mount point that can be defined in thenuxt.config.ts
.The 'non-cookie' storageTypes allow two more configs:
The
sessionInactivityMaxAge
is used to determine orphaned sessions that can be deleted withcleanupOrphanedUserSessions
, which can run in a scheduled nitro task (unfortunately not on the edge) or in a server middleware or a specific route.The session data is not encrypted to the server which can be discussed as the stored data is obvious at least in transfer to the server side anyway.
What this PR can not do, is determining multiple sessions of one user as this would need a server side user id, independent from the auth provider used (since one user could have multiple different providers).