You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What Operating System are you using (both controller, and any agents involved in the problem)?
Master is on : OS Linux - 5.4.0-1060-aws
No other system involved to reproduce the issue
Reproduction steps
configure Jenkins to use "Azure Active Directory Matrix-based security"
set no specific rights for "anonymous users" and for "Authenticated users"
set all rights for an existing AD user :
I tested this in an isolated context, by creating a new job and choosing "Do not inheirt permissions grants from other ACLs", then setting the permissions as describe thereabove :
Just add "read" permission to "Authenticated users"
Try again to read job history by running the API call again, you'll get a valid result.
It seems that giving rights to a specific user is not well considered. Needing to give also rights to a larger group seems to be a regression and not conform to "least privilege" security common practices.
Thanks for your help on that.
Expected Results
Individual rights should override more global ones : extending rights for a specific user should be possible.
Actual Results
Individual rights are overriden by "Authenticated users" ones.
Anything else?
No response
The text was updated successfully, but these errors were encountered:
aubertaa
changed the title
Rights for "Authenticated Users" are overriding indivual rights
Rights for "Authenticated Users" are overriding individual rights
Feb 18, 2022
Ordinary developpers that have a valid AD account are correctly assigned their permissions.
People belonging to the group Jenkins Admin are correctly assigned their permissions.
The user Jenkins Bot doesn't get it's permission. i.e.: Jenkins Bot is never recognized to have Run/Delete permission. Though, if I add Run/Delete in the group authenticated, Jenkins Bot is allowed to delete runs.
I'm pretty sure it's either those two things:
The user never gets mapped properly and it's silently defaulting to the group authenticated.
There's a bug in the code where the group authenticated is overpowering permissions from single user.
Jenkins and plugins versions report
Environment
What Operating System are you using (both controller, and any agents involved in the problem)?
Master is on : OS Linux - 5.4.0-1060-aws
No other system involved to reproduce the issue
Reproduction steps
I tested this in an isolated context, by creating a new job and choosing "Do not inheirt permissions grants from other ACLs", then setting the permissions as describe thereabove :
You'll get a 404.
It seems that giving rights to a specific user is not well considered. Needing to give also rights to a larger group seems to be a regression and not conform to "least privilege" security common practices.
Thanks for your help on that.
Expected Results
Individual rights should override more global ones : extending rights for a specific user should be possible.
Actual Results
Individual rights are overriden by "Authenticated users" ones.
Anything else?
No response
The text was updated successfully, but these errors were encountered: