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

Job/Configure permission required to configure jobs

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Minor
    • Resolution: Duplicate
    • Labels:
      None
    • Environment:
      Jenkins ver. 2.190.3
      Bitbucket Server Integration 1.0.3
      Matrix Authorization Strategy Plugin 2.5
      Role-based Authorization Strategy 2.15
      LDAP Plugin 1.21
    • Similar Issues:
    • Released As:
      1.0.4

      Description

      I've got Jenkins break issue using "Matrix Authorization Strategy Plugin" in project.
      If user tries to create or configure job in project without global "Job/Configure permission" in his role, it causes Jenkins break. "project-based security" option in project itself not affects this behaviour.
      Log:

      Dec 15, 2019 1:54:17 AM INFO org.eclipse.jetty.server.handler.ContextHandler$Context log
      While serving http://jenkins.local/job/test/job/test/descriptorByName/com.atlassian.bitbucket.jenkins.internal.scm.BitbucketSCM/checkCredentialsId: hudson.security.AccessDeniedException2: test_user is missing the Job/Configure permission
      

      How to reproduce it:
      You can try to create or configure job in project without global "Job/Configure permission" for this project in user's role.

        Attachments

          Issue Links

            Activity

            Hide
            jthornsen Jeff Thornsen added a comment -

            This is affecting my instance as well.  It seems there is a bug or limitation in Atlassian's Jenkins-Bitbucket integration plugin that requires all users to have global Job/Configure permissions.  Simply having permissions at the Folder Level isn't sufficient, and causes all kinds of weird behavior in the UI (like the configure page loading but half the buttons are non-operational, or getting the "Oops" page with the burning Jenkins logo).

             

             

            Show
            jthornsen Jeff Thornsen added a comment - This is affecting my instance as well.  It seems there is a bug or limitation in Atlassian's Jenkins-Bitbucket integration plugin that requires all users to have global Job/Configure permissions.  Simply having permissions at the Folder Level isn't sufficient, and causes all kinds of weird behavior in the UI (like the configure page loading but half the buttons are non-operational, or getting the "Oops" page with the burning Jenkins logo).    
            Hide
            royxszhou2010 roy zhou added a comment -

            we also have this issue with cloudbees jenkins v2.204.2.2 and the folder plugin version 6.9, Bitbucket server integration plugin version is 1.1.0. Is there a fix for it yet ?  but it looks like ok for freestyle job, issue only happens when we try to create pipeline jobs.

            Show
            royxszhou2010 roy zhou added a comment - we also have this issue with cloudbees jenkins v2.204.2.2 and the folder plugin version 6.9, Bitbucket server integration plugin version is 1.1.0. Is there a fix for it yet ?  but it looks like ok for freestyle job, issue only happens when we try to create pipeline jobs.

              People

              • Assignee:
                mhenschke_atlassian Martin Henschke
                Reporter:
                nrzway Roman T
              • Votes:
                1 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: