Bug 48607 - UMC / Portal not working on due to Content Security Policy
UMC / Portal not working on due to Content Security Policy
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: UMC (Generic)
UCS 4.3
Other Linux
: P5 normal (vote)
: ---
Assigned To: UMC maintainers
UMC maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2019-02-04 13:59 CET by Florian Best
Modified: 2021-05-14 16:33 CEST (History)
2 users (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 5: Major Usability: Impairs usability in key scenarios
Who will be affected by this bug?: 5: Will affect all installed domains
How will those affected feel about the bug?: 2: A Pain – users won’t like this once they notice it
User Pain: 0.286
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional): Browser compatibility, Usability
Max CVSS v3 score:


Attachments
Screenshot (66.87 KB, image/png)
2019-02-04 14:04 CET, Florian Best
Details
Screenshot Firefox (146.42 KB, image/png)
2019-02-25 12:13 CET, Florian Best
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Florian Best univentionstaff 2019-02-04 13:59:12 CET
It seems dojo makes a request to 'https://dojotoolkit.org/' during startup.
This request is blocked by our Content-Security-Policy.

Refused to connect to 'https://dojotoolkit.org/' because it violates the following Content Security Policy directive: "connect-src 'self' https://ucs-sso.demo.univention.de/ http://ucs-sso.demo.univention.de/".


dojo.js:20 Uncaught DOMException: Failed to execute 'open' on 'XMLHttpRequest': Refused to connect to 'https://dojotoolkit.org/' because it violates the document's Content Security Policy.
    at Object.native-xhr2-blob (https://demo.univention.de/univention/js/dojo/dojo.js:502:185)
    at l.has (https://demo.univention.de/univention/js/dojo/dojo.js:3:211)
    at https://demo.univention.de/univention/js/dojo/dojo.js:502:312
    at ia (https://demo.univention.de/univention/js/dojo/dojo.js:20:170)
    at ia (https://demo.univention.de/univention/js/dojo/dojo.js:19:416)
    at ia (https://demo.univention.de/univention/js/dojo/dojo.js:19:416)
    at https://demo.univention.de/univention/js/dojo/dojo.js:20:425
    at ja (https://demo.univention.de/univention/js/dojo/dojo.js:20:292)
    at ga (https://demo.univention.de/univention/js/dojo/dojo.js:20:367)
    at Pa (https://demo.univention.de/univention/js/dojo/dojo.js:12:308)
Comment 2 Florian Best univentionstaff 2019-02-04 14:59:54 CET
Happens also with Google Chrome 72.0.3626.81.
Comment 3 Florian Best univentionstaff 2019-02-25 09:31:48 CET
Could be the problem why your selenium tests don't work?!
Comment 4 Florian Best univentionstaff 2019-02-25 12:13:50 CET
Created attachment 9862 [details]
Screenshot Firefox
Comment 5 Florian Best univentionstaff 2019-02-25 12:15:11 CET
Firefox 65 is affected as well.
Comment 6 Ingo Steuwer univentionstaff 2021-05-14 15:40:55 CEST
This issue has been filed against UCS 4.3.

UCS 4.3 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.