-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Monaco Editor does not work on ThingWorx 9.3.17-b2768 with CSP enabled #57
Comments
We've just updated to ThingWorx 9.6.1 and also noticed this problem coming from 9.3.9.
You can manually Hope this helps 🤞 |
Thank you for sharing your experience! I tried using your values and checked if the CSP has been modified using https://csp-evaluator.withgoogle.com/ sadly, it does not seem to be working for me
|
Hi NicciZar, |
Hi JanKerkhofs, thank you! This works! Maybe this should be added to the Readme of the Addon so other users can configure their TWX CSP accordingly. |
After updating to version ThingWorx 9.3.17-b2768 PTC enforces usage of their ContentSecurityPolicy found within PlatformSubsystem.
It seems like the default settings makes it impossible for MonacoEditor to load the newComposer.bundle.js file.
CSP is a key security tool web browsers use to help secure against cross-site scripting (XSS), Clickjacking, and other data injection attacks. CSP works by injecting CSP headers from the ThingWorx Platform into the web browser to control what dynamic data and resources the browser can load and from what domains.
https://support.ptc.com/help/thingworx/platform/r9/en/#page/ThingWorx/Help/Composer/Security/ContentSecurityPolicy.html
It is configurable from within Thingworx but I am unsure which exact setting is the correct one.
The text was updated successfully, but these errors were encountered: