-
Notifications
You must be signed in to change notification settings - Fork 7
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
SameSite Config Option for Cookie #35
Conversation
Develop to master
Develop to master - fix CSRF errors on re-login
- Added config option `ckanext.csrf_filter.same_site` to set the cookie Samesite attribute.
- Added SameSite config to readme.
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 for the contribution!
Could I get you to target the 'develop' branch instead of 'main'? That's used in our development environments to try features out.
- Added config option for regex matching exlcusions to CSRF token checks.
Regex Rules to Exempt from Token Checks
Hi @JVickery-TBS, Due to github cost cutting, they disable github actions on forked repo's. Can you enable github actions on your fork and retrigger a build so cicd pipeline can run letting us know if tests pass, etc. https://github.com/open-data/ckanext-csrf-filter/actions |
@duttonw Workflows enabled on our fork now. Did you want me to add on dispatch and on PR to the test yaml? |
- Allow response generators to return and not be edited to insert any token.
Co-authored-by: Ian Ward <[email protected]>
…ream Allow Response Streaming from Generators
Just splitting this up into multiple PRs now. |
And this one: #37 (includes the |
And finally this one: #38 |
Adds
ckanext.csrf_filter.same_site
config option which defaults to'None'
and uses it in setting the token cookie. Asserts the allowed values of 'Strict', 'Lax', and 'None'This should solve the issue: #28