[MAGNOLIA-8271] Set session cookies as secure & http-only by default Created: 22/Dec/21 Updated: 23/Dec/21 |
|
| Status: | Accepted |
| Project: | Magnolia |
| Component/s: | core |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Mikaël Geljić | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | security | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Template: |
|
||||
| Acceptance criteria: |
[ ]*
Verify impact, then remediation via sys-prop on local development instances
[ ]*
Verify in context of Magnolia behind a reverse-proxy (talking to it over http)
[ ]*
Verify on one of our current cloud subs (magnolia-pd no longer active) or on PaaS, together with SSO
[ ]*
Verify Vaadin Admincentral session tracking is not impacted (does not rely on accessing JSESSIONID programmatically on the client)
|
||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||
| Release notes required: |
Yes
|
||||
| Documentation update required: |
Yes
|
||||
| Description |
—via had, see thread in #security Therefore we consider setting cookies as secure & http-only (not for client-scripts) by default, programmatically.
|