Details
-
Story
-
Status: Closed (View Workflow)
-
P2
-
Resolution: Done
-
None
-
-
CP: sprint 91, CP: sprint 92, CP: sprint 113, CP: sprint 114
-
5
-
Core: Platform
Description
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
TestRail: Results
Attachments
Issue Links
- blocks
-
MODLOGSAML-58 Arbitrary URL Redirection in SAML Response
-
- Closed
-
-
MODLOGSAML-59 Umbrella: Cross-Site Request Forgery (CSRF) in SSO Flow
-
- Closed
-
- is blocked by
-
OKAPI-876 CORS delegation doesn't work with preflight/OPTIONS requests
-
- Closed
-
-
OKAPI-1016 Support delegate preflight request
-
- Closed
-
-
RMB-656 NPE at startup when an OPTIONS endpoint is defined in RAML
-
- Closed
-
-
STCOR-544 Set credentials: include on fetch to /saml/login
-
- Closed
-
-
STCOR-545 Pass tenant info when making saml login call
-
- Closed
-
- relates to
-
FOLIO-2956 Spike: Provide guidelines for use of Content Security Policy headers with FOLIO
-
- Blocked
-
-
MODLOGSAML-103 CORS Access-Control-Allow-Credentials for /saml/login and /saml/callback
-
- Closed
-
-
OKAPI-847 Conditionally defer CORS handling to module when invoked via passthrough API
-
- Closed
-