Details
-
Sub-task
-
Resolution: Fixed
-
L3 - Default
-
None
-
None
-
None
Description
Problem
- It is hard to perform modifying requests for the user because of the absence of the CSRF token
- Previously, the AngularJS Cockpit took care of providing the CSRF token
Reasoning
- The getting started experience for users would be better if the CSRF token can be accessed directly from the render method
- CSRF Prevention is not manifested as a standard so the implemented behavior differs from webapp to webapp (we use the `Set-Cookie` approach) [1]
- From a user's perspective, it is hard to learn how the CSRF token can be accessed
Solution
Pass the CSRF token into the render method.