-
Bug
-
Resolution: Unresolved
-
Critical
-
None
Using Authorize Project plugin I have setting we have "Project Default build Authorization" set to "Run as User who Triggered Build".
Then I have project roles letting particular users to run specific jobs. To allow said people to also build on the nodes I assign to them Slave role (see assign_roles.png). That Slave role is allowed to build on ".*" nodes (see manage_roles.png). But still when project is triggered from such a user, in the queue a message can be seen:
> 'myusername' lacks permission to run on 'my-node-name-1'
My workaround is to allow global Agent/Build permission to everybody but this is not ideal.
Jenkins 2.190.3
Authorize Project 1.3.0
Role-based Authorization Strategy 2.13
- is related to
-
JENKINS-68105 Group permissions not recognised by Authorize Project
-
- Open
-
[JENKINS-61902] "authenticated" group doesn't work with Authorize Project plugin
Attachment | Original: manage_roles.png [ 50947 ] |
Attachment | New: manage_roles.png [ 50949 ] |
Summary | Original: Slave roles not respected with Authorize Project plugin | New: "authenticated" group doesn't work with Authorize Project plugin |
Assignee | Original: ikedam [ ikedam ] | New: akostadinov [ akostadinov ] |
Link | New: This issue is related to JENKINS-68105 [ JENKINS-68105 ] |