Is your feature request related to a problem? Please describe.
Secured cookies (session and CSRF) are enforced for the LMS when enabling HTTPS, via these configuration lines. However, CMS does not get secured cookies. This is a security requirement asked by organizations with strong security policies.
Describe the solution you'd like
I would like to move this configuration block to the common_all file so the CMS gets the benefits of the secured cookies configuration.
Describe alternatives you've considered
For now, we are handling this via Tutor plugins. However, I consider it to be the type of change that could be offloaded into the Tutor core.
Is your feature request related to a problem? Please describe.
Secured cookies (session and CSRF) are enforced for the LMS when enabling HTTPS, via these configuration lines. However, CMS does not get secured cookies. This is a security requirement asked by organizations with strong security policies.
Describe the solution you'd like
I would like to move this configuration block to the common_all file so the CMS gets the benefits of the secured cookies configuration.
Describe alternatives you've considered
For now, we are handling this via Tutor plugins. However, I consider it to be the type of change that could be offloaded into the Tutor core.