mwebber commented on Improvement JENKINS-19934

>> Global roles override any project-specific permissions.
Understood. My problem is when the user is not assigned to any global role.

Here's the problem case:

  • The main Jenkins configuration has "Restrict project naming" on, with "Role-Based Strategy" selected.
  • I have a project role called "Controls-Administrator" with a jobname pattern of "Controls.*". The role has all job permissions set.
  • user xzl80115 is not assigned to any global role
  • user xzl80115 is assigned to project role "Controls-Administrator"

In this case, I would expect that user xzl80115 could create jobs named something like "Controls_abc". However, the "New View" link to create a job is never displayed, and if the user manually enters the URL http://<jenkins>/newJob then he gets told he does not have permission to create any jobs.

It may be relevant that users authenticate using the CAS plugin and the CAS 2.0 protocol.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to