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

"Access Denied" {user} is missing the N/A/Generic Configure permission

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • parameterized-scheduler-plugin
    • None
    • Jenkins 2.346.3 plugin version 1.1
    • parameterized-scheduler:1.2

      User is granted full job admin access but NOT JENKINS ADMIN access will have an "Access Denied" rendered in the job configure page, but is still able to change the configuration and save the revised job config.

        1. ParameterizedSchedulerIssue.png
          ParameterizedSchedulerIssue.png
          29 kB

          [JENKINS-69691] "Access Denied" {user} is missing the N/A/Generic Configure permission

          George Yu added a comment -

          The same problem occurred to me, after upgrading to Jenkins 2.361.1

          George Yu added a comment - The same problem occurred to me, after upgrading to Jenkins 2.361.1

          Brian added a comment - - edited

          I had the same error using the same parameterized-scheduler plugin. It might be an issue specifically with this plugin. Jenkins 2.319.3

          Brian added a comment - - edited I had the same error using the same parameterized-scheduler plugin. It might be an issue specifically with this plugin. Jenkins 2.319.3

          Curtis added a comment -

          I upgraded to Jenkins 2.361.3.2 this week, and users are seeing this "N/A/GenericConfigure permission" error after updating a job configured with the parameterized-scheduler plugin.

          Curtis added a comment - I upgraded to Jenkins 2.361.3.2 this week, and users are seeing this "N/A/GenericConfigure permission" error after updating a job configured with the parameterized-scheduler plugin.

          Allan BURDAJEWICZ added a comment -

          Seems to be introduced by this https://github.com/jenkinsci/parameterized-scheduler-plugin/pull/154. We should not check for the Generic hudson.security.Permission.CONFIGURE but hudson.model.Item#CONFIGURE.

          Allan BURDAJEWICZ added a comment - Seems to be introduced by this https://github.com/jenkinsci/parameterized-scheduler-plugin/pull/154 . We should not check for the Generic hudson.security.Permission.CONFIGURE but hudson.model.Item#CONFIGURE .

          Robyn Sandova added a comment -

          We are seeing this with Jenkins 2.346.2

          Robyn Sandova added a comment - We are seeing this with Jenkins 2.346.2

          Michael Jung added a comment -

          The PR is open for quite some time now (practically no comment). What is keeping it from being merged and released?

          Michael Jung added a comment - The PR is open for quite some time now (practically no comment). What is keeping it from being merged and released?

          Ian Panzer added a comment -

          We are hitting this bug after we updated to 361.2 Any chance it could be fixed?

          Ian Panzer added a comment - We are hitting this bug after we updated to 361.2 Any chance it could be fixed?

          Allan BURDAJEWICZ added a comment -

          This should be fixed in version 1.2 https://github.com/jenkinsci/parameterized-scheduler-plugin/releases/tag/parameterized-scheduler-1.2

          Allan BURDAJEWICZ added a comment - This should be fixed in version 1.2 https://github.com/jenkinsci/parameterized-scheduler-plugin/releases/tag/parameterized-scheduler-1.2

            allan_burdajewicz Allan BURDAJEWICZ
            lfiorino Lou Fiorino
            Votes:
            5 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated:
              Resolved: