-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add sameSite option to sessions #5774
Add sameSite option to sessions #5774
Conversation
🦋 Changeset detectedLatest commit: 7611881 The changes in this PR will be included in the next version bump. This PR includes changesets to release 11 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/keystonejs/keystone-next-docs/n7oEeBphfkrNLyFYGzTGXNWE59qB |
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit 7611881:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great, thanks @jonowu!
thanks for this! |
Adds a
sameSite
option to the session options for cookies. Can be one oftrue
,false
,'strict'
,'lax'
or'none'
as per Mozilla docs. The option defaults to'lax'
which is in line with existing behaviour.This option will be useful for users who have deployed their keystone instance to a different site from their frontend, e.g. hosting keystone on
example.herokuapp.com
with the frontend onexample.vercel.app
.