-
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
-
[JENKINS-30574] Support global default authorization strategy in Authorize Project
Link |
New:
This issue is related to |
Description |
Original:
Due to security reasons, sometimes Jenkins admins may want to completely restrict running jobs as a system. 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 |
New:
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 |
Link |
New:
This issue is related to |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Assignee | New: ikedam [ ikedam ] | |
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
Link |
New:
This issue duplicates |
Workflow | Original: JNJira [ 165686 ] | New: JNJira + In-Review [ 209260 ] |