[CLI] Set default CSRF protection for sessions in the configuration #594
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.
Issues
none
option for theSameSite
cookie attribute. Developers should be able to use this value.@TokenRequired({ cookie: true })
) might not be aware of CSRF attacks and how to protect against them. We should set up a default protection for this in every new project.Solutions and steps
CookieOptions
interface.createapp
will include a default CSRF protection for sessions : the cookie attributeSameSite
will be set tolax
.Checklist