If the "Prevent cross site forgery request exploit" option is selected in the "Configure global" security page and a change is made and saved on the global settings page - the cross site forgery prevention option is deactivated.
This is causing issues with post-commit hooks that pass the API token as well as the crumb in the HTTP header when making RESTful calls to Jenkins.
- duplicates
-
JENKINS-17087 Saving Jenkins Global Config wipes out the crumb issuer settings in the Global Security Config
-
- Resolved
-
[JENKINS-16495] Saving global settings causes cross site request forgery option to be disabled
Assignee | New: Dominik Bartholdi [ imod ] |
Priority | Original: Minor [ 4 ] | New: Major [ 3 ] |
Assignee | Original: Dominik Bartholdi [ imod ] | New: Dominik Bartholdi [ domi ] |
Link |
New:
This issue duplicates |
Resolution | New: Duplicate [ 3 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Workflow | Original: JNJira [ 147317 ] | New: JNJira + In-Review [ 192335 ] |