-
Notifications
You must be signed in to change notification settings - Fork 1
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
hotfix: set SESSION_COOKIE_SECURE = True #695
Conversation
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.
LGTM.
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.
I am unavailable to test yet. I approve it because I don't anticipate an issue. And Django says it should be True
(even though default it to False
).
https://docs.djangoproject.com/en/3.2/ref/settings/#std-setting-SESSION_COOKIE_SECURE
If every CMS needs this, then this should also be done off on a branch off of v3.11.5 tag, so I can make a v3.11.6 release. Most sites are running v3.11. Core-CMS does not have a stable v3.12 yet. |
To get TACC/Core-CMS#695. If UI demo breaks, see TACC/Core-CMS#692.
- mimics TACC/Core-CMS#695 - alternative to #196
- mimics TACC/Core-CMS#695 - alternative to #196
- mimics TACC/Core-CMS#695 - alternative to #301
- mimics TACC/Core-CMS#695 - alternative to #301
Overview
Sets
SESSION_COOKIE_SECURE = True
to resolve a flag set by an ISO security audit.Related
Testing
UI