Webinar Q&A: Role-Based Access Control for the Enterprise with Jenkins
Thank you to everyone who joined us on our webinar, the recording is now available.
Below are several of the questions we received during the webinar Q&A:
Q: How do you admin the groups? Manually or is this there LDAP involved?
A: You can decide if you want to create internal Jenkins users/groups or import users and groups from your LDAP server. In this case you can use the LDAP Jenkins plugin to import them but you still need to manage them manually using Jenkins. Each external group has to match an internal Jenkins group so that you can assign a role to it. Roles are defined in Jenkins regardless the origin of users and groups (internal or external).
Q: Is there any setting for views, instead folders? Are the RBAC settings available for views?
A: In short, yes. The RBAC plugin supports setting group definitions over the following objects:
A: The standard way in which you should associate multiple Jenkins jobs with the same group is through folders. However, remember that you can also create groups at job level.
Q: If we convert from the open source 'role-based strategy' plugin to this role-based plugin, will it translate the roles automatically to the new plugin?
A: Roles are not converted automatically, so you will need to set-up your new rules with the RBAC plugin.
A: You can contact us in the public mail email@example.com .
Overall configure permissions would also allow users to modify any setting on the Jenkins master.
Follow Valentina on Twitter .
Félix Belzunce is a solutions architect for CloudBees based in Europe. He focuses on continuous delivery. Read more about him on his Meet the Bees blog post and follow him on Twitter.
Stay up to date
We'll never share your email address and you can opt out at any time, we promise.