Status: Closed (View Workflow)
Resolution: Not A Defect
Jenkins 2.204.2 JDK Oracle 8 (202)
I use "Project-based Matrix Authorization Strategy ".
I set the group "Authenticated Users" with permission overall read, job read, credential view, view read.
If a user try to call an api with a token like: `curl -u myuser:123456 -v -H 'Accept: application/json' https://jenkins/api/json` then the response is 403 with a HTML body in which I have "myuser is missing the Overall/Read permission"
If I add a "overall read" permission on the "myuser" itself, then the api is working (200 + data)
Does this mean that authenticating via a token do not add the 'authenticated' group ? Is this wanted? if so why not a "tokens" group ?
From your answer, Jenkins do have a bug. If I set Overall/Read to "authenticated" user, then I expect even with a token, such policy is executed hence a user without other permission would be able to call jenkins api. It is not the case.
gregoirew Adding the authenticated pseudo-group is the responsibility of the plugin providing authentication (i.e. security realm). So there seems to be a bug here, I agree, but not in matrix-auth.
Is there a generic specific handler for token somewhere or each authentication handler duplicate the token authentication management ?
Overall/Read grants basic access to Jenkins. Nothing more. Users without that basically cannot do anything, except in very limited circumstances.
Users have a group or don't, the method of authentication doesn't change what they're authorized to do.