-
New Feature
-
Resolution: Fixed
-
Major
Due to security reasons, sometimes Jenkins admins may want to completely restrict running jobs as a system/anonymous and setup custom security limitations. In such case it would be useful to add the following features:
- Global default strategy (if no one configured at the project level)
- Enforced global strategy, which prevents setting other strategies on the project level
- duplicates
-
JENKINS-22949 QueueItemAuthenticator fallback behavior cleanup
-
- Resolved
-
- is related to
-
JENKINS-22949 QueueItemAuthenticator fallback behavior cleanup
-
- Resolved
-
-
JENKINS-32770 Provide a mechanism to run specific projects as ACL.SYSTEM
-
- Closed
-
jglick FYI the authorize project plugin currently assumes a strategy returning null will get run as SYSTEM:
https://github.com/jenkinsci/authorize-project-plugin/blob/master/src/test/java/org/jenkinsci/plugins/authorizeproject/ProjectQueueItemAuthenticatorTest.java#L145
(of course that is incorrect, returning null means fall through to the next strategy... and if you fall off the end of all strategies then you default to SYSTEM modulo
JENKINS-22949because of backwards compatability)