Skip to content
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

Enforce that there are no CSP violations when csp.rule is defined #1749

Merged
merged 1 commit into from
Oct 25, 2024

Conversation

basil
Copy link
Member

@basil basil commented Oct 1, 2024

Building on #1743, when csp.rule is defined, we not only enable CSP in restrictive mode, but also we verify at the end of each test that there are no violations logged on the report page. Currently skipped for two plugins that have known violations:

@basil basil force-pushed the csp-report-only branch 4 times, most recently from a2fb4ed to 8d5d712 Compare October 8, 2024 14:46
@basil basil force-pushed the csp-report-only branch 8 times, most recently from 42648a9 to a3a6ccf Compare October 16, 2024 21:25
@basil basil force-pushed the csp-report-only branch 8 times, most recently from 1767de4 to 7cd13c6 Compare October 25, 2024 16:02
@basil basil changed the title Run ATH with CSP (report only) Enforce that there are no CSP violations Oct 25, 2024
@basil basil changed the title Enforce that there are no CSP violations Enforce that there are no CSP violations when csp.rule is defined Oct 25, 2024
@basil basil force-pushed the csp-report-only branch 3 times, most recently from 3a42540 to 21e7a32 Compare October 25, 2024 16:47
@basil basil marked this pull request as ready for review October 25, 2024 18:46
@basil basil merged commit ebdf63f into jenkinsci:master Oct 25, 2024
25 checks passed
@basil basil deleted the csp-report-only branch October 25, 2024 19:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant