OPSEXP-3507 Add unsafe-eval to default CSP for webapps #1265
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
OPSEXP-3507
This PR adds the
'unsafe-eval'directive to the default Content Security Policy (CSP) for webapp locations in the nginx configuration.Changes Made
Updated the
nginx_security_headers_webappsCSP policy inroles/nginx/defaults/main.ymlto include'unsafe-eval'in thescript-srcdirective:Before:
After:
Affected Locations
This change applies to the following webapp endpoints that use the
nginx_security_headers_webappsconfiguration://api-explorer//control-center//workspace/Test Updates
Updated the molecule test expectations in
roles/nginx/molecule/default/verify.ymlfor the/workspace/location to match the new CSP policy with'unsafe-eval'.Notes
/share/location already had'unsafe-eval'configured vianginx_security_headers_shareand is unaffected by this change/alfresco/repository location continues to usenginx_security_headers_repositorywhich has no CSP policy by design💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.