Details
-
Improvement
-
Resolution: Done
-
Neutral
-
6.2.12
-
-
Empty show more show less
-
Yes
-
Yes
Description
After reviewing the CSRF concept in Magnolia, we concluded couple solutions:
In MAGNOLIA-8209 (just FYI here):
- First, reduce the amount of cookies generated for every requests. Tentatively recycle the cookie name (sub-domain only), and update its value?
In this ticket:
- Reconsider applying the token generation to everything, unless the Form loginHandler's allowedMethods includes GET (disabled by default since MAGNOLIA-8115).
- Split implementation of synchronizer-pattern vs. double-submit cookie pattern into two CSRF filters, with their own bypasses.
See SUPPORT-13766 for the original bug report.
As QA we should verify the solution also positively impacts the amount of cookies/headers size.
Checklists
Acceptance criteria
Attachments
Issue Links
- clones
-
MAGNOLIA-8209 CSRF Header sent with all responses
-
- Closed
-
- relates to
-
MAGNOLIA-8226 DOC: Update CSRF filter implementation
-
- Closed
-
- split to
-
MAGNOLIA-8232 Intercept login redirects to reduce bypasses for the login-CSRF filter
-
- Accepted
-
- to be documented by
-
MAGNOLIA-8226 DOC: Update CSRF filter implementation
-
- Closed
-
- mentioned in
-
Page Loading...