|
cforce created JENKINS-12432:
-------------------------------- Summary: Mix between Matrix based and Role based Key: JENKINS-12432 URL: https://issues.jenkins-ci.org/browse/JENKINS-12432 Project: Jenkins Issue Type: New Feature Components: role-strategy Reporter: cforce Assignee: Romain Seguy In our company we have defined roles which defined rights. A person or group can have a role per project. The mapping would be rights N:N roles roles N:N jobs user/group N:N projects N:N roles So we would need to be able to define project roles as container for rights and this roles are valid for all jobs. On Job level we wanna set which user/group has which role. Filtering roles on Job-Name level doesn't make sense, because we wanna grant creating jobs to all divisions. If the Job Name can control to get access on other jobs, this will be a secuity issue for us. For us it would be quite ok, to be able to select user/group to roles mapping on job level. A role in project shall be allpowed to itself set additional roles for users. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
[ https://issues.jenkins-ci.org/browse/JENKINS-12432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Seguy reassigned JENKINS-12432: -------------------------------------- Assignee: Daniel Petisme (was: Romain Seguy) > Mix between Matrix based and Role based > --------------------------------------- > > Key: JENKINS-12432 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12432 > Project: Jenkins > Issue Type: New Feature > Components: role-strategy > Reporter: cforce > Assignee: Daniel Petisme > > In our company we have defined roles which defined rights. A person or group can have a role per project. > The mapping would be > rights N:N roles > roles N:N jobs > user/group N:N projects N:N roles > So we would need to be able to define project roles as container for rights and this roles are valid for all jobs. > On Job level we wanna set which user/group has which role. > Filtering roles on Job-Name level doesn't make sense, because we wanna grant creating jobs to all divisions. If the Job Name can control to get access on other jobs, this will be a secuity issue for us. > For us it would be quite ok, to be able to select user/group to roles mapping on job level. A role in project shall be allpowed to itself set additional roles for users. > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira |
| Powered by Nabble | See how NAML generates this page |
