-
Bug
-
Resolution: Unresolved
-
Major
In order to be included in Permission.getAll(), a Permission needs to be initialized in a static block inside an @Extension or otherwise definitely loaded during startup.
The visible symptom is that you might configure an authorization strategy such as matrix with all permissions granted, then go back later and see SCM/Tag missing, because it was unknown earlier.
- is blocking
-
JENKINS-16502 Permission to see an agent
-
- Reopened
-
- is related to
-
JENKINS-15484 New permission controlling ability to configure your own User
-
- Open
-
-
JENKINS-37546 When dynamic plugin load fails, PermissionGroups are not being cleaned up
-
- Open
-
-
JENKINS-21336 ADMINISTER should not imply RUN_SCRIPTS
-
- In Progress
-
-
JENKINS-27134 Permission for input approval, or choice of Jenkins-specific group as submitter
-
- Open
-
- links to
[JENKINS-17200] SCM.TAG permission not eagerly loaded
Link | New: This issue is related to JENKINS-15484 [ JENKINS-15484 ] |
Labels | Original: permissions | New: api permissions |
Link | New: This issue is blocking JENKINS-16502 [ JENKINS-16502 ] |
Link | New: This issue is related to SECURITY-91 [ SECURITY-91 ] |
Link | New: This issue is related to JENKINS-27134 [ JENKINS-27134 ] |
Labels | Original: api permissions | New: 2.0 api permissions |
Labels | Original: 2.0 api permissions | New: 2.0-rejected api permissions |
Link | New: This issue is related to JENKINS-21336 [ JENKINS-21336 ] |
Remote Link | New: This issue links to "Related discussion in PR 882 (Web Link)" [ 14640 ] |
Workflow | Original: JNJira [ 148032 ] | New: JNJira + In-Review [ 177067 ] |