Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-43360

Gitlab Authorization Fine-Graining



    • Improvement
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • gitlab-oauth-plugin
    • None
    • Jenkins 2.53, GitLab 9.0.0


      First things first: We successfully use GitLab OAuth for Jenkins and it works like a charm. Thanks for your great work!

      Now the improvements required, before we can let guests, reporters and developers access the Jenkins server:

      Our projects are all private. The default user rights connected with the above three GitLab roles allow modifying and even deleting the project related build jobs. As we assign these roles to project stakeholders that not always should have these permissions,

      we're looking for a way to restrict their access to read-only, or read and build only on a per GitLab project role base. (Or at least having the default access granted to the above roles limited in that manner.)

      As your plugin unfortunately does not provide these features, we still have to use matrix based permissions, which is a pain with growing job and user numbers. 



          mario_steinitz Mario Steinitz created issue -
          andhbr Jack Black made changes -
          Field Original Value New Value
          Assignee Mohamed El Habib [ elhabib_med ] Andras Hobar [ andhbr ]
          andhbr Jack Black made changes -
          Assignee Andras Hobar [ andhbr ] Mohamed El Habib [ elhabib_med ]


            elhabib_med Mohamed El Habib
            mario_steinitz Mario Steinitz
            1 Vote for this issue
            2 Start watching this issue