[SDK-3808] Optionally sign the session store cookie #419
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.
Description
Add an option
signSessionStoreCookie
(defaultfalse
) - when true and using a custom session store, the session store cookie will be signed. e.g.The default session id is a cryptographically secure random value, but this is useful when you want to override
genid
and you are only generating a unique value, not a cryptographically secure random value.Also adding a
requireSignedSessionStoreCookie
config option to allow zero down time migration to signed session store cookies.fafa0e0 The first commit is just moving some code into another file to make it easier to share
d1c3dc0 This is the main commit that implements signed session store cookies
References
express-session docs
genid
Testing
Checklist