Set strong CSP: enforce for development, report-only for production#1012
Set strong CSP: enforce for development, report-only for production#1012labkey-adam merged 2 commits intorelease25.3-SNAPSHOTfrom
Conversation
|
This is unlikely to actually impact existing installs. Should we instead or also make this the default in |
I don't actually know how these properties get applied on production servers. |
Oh, existing installs... because they don't replace application.properties every upgrade? |
Exactly. It has their DB settings and other install-specific config. Ideally they might check the new version in the download and merge them together, but I doubt that happens very often |
|
@labkey-jeckels please review the latest. I didn't see much value in keeping the comments in the code version. |
labkey-jeckels
left a comment
There was a problem hiding this comment.
It's unfortunate to have another copy of CSP checked in. Maybe we can soon have both a report and enforce specified solely in LabKeyServer.java. We'd need to conditionalize the report-uri
Rationale
For 25.3, we've decided to configure CSP r11 (report-only) by default for all on-premise deployments and CSP e11 (enforce) for all development deployments