Done
Details
Assignee
Hongwei JiHongwei JiReporter
Craig McNallyCraig McNallyPriority
P2Story Points
5Sprint
NoneDevelopment Team
Core: PlatformFix versions
TestRail: Cases
Open TestRail: CasesTestRail: Runs
Open TestRail: Runs
Details
Details
Assignee
Hongwei Ji
Hongwei JiReporter
Craig McNally
Craig McNallyPriority
Story Points
5
Sprint
None
Development Team
Core: Platform
Fix versions
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created May 21, 2020 at 1:40 PM
Updated July 8, 2021 at 4:10 PM
Resolved May 24, 2021 at 12:01 PM
Overview
This is a follow-up to the investigation done for MODLOGSAML-59 / MODLOGSAML-58 and covers implementation of the design outlined on the wiki
Acceptance Criteria
CORS handling is done by the module
* tenant-specific origin whitelist
* Access-Control-Allow-Origin is set to the origin, not *
* Access-Control-Allow-Credentials is set to true for /saml/login
CSRF prevention is implemented via RelayState and a associated cookie