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

Add a Jenkins.CONFIGURE permission to be able to configure Jenkins without ADMINISTER

    XMLWordPrintable

Details

    • New Feature
    • Status: Resolved (View Workflow)
    • Minor
    • Resolution: Fixed
    • core
    • None
    • Jenkins 2.222

    Description

      I create this Jira to follow the work in progress about "Sensible permission" related to the JEP that is in draft status for now and can be found here https://github.com/jenkinsci/jep/pull/249

      The main goal is to have a new permission called `Jenkins.MANAGE` to allow management of Jenkins. All sensible or security related items are restricted to `Jenkins.ADMINISTER`.

      The draft PR with this new permission implementation is https://github.com/jenkinsci/jenkins/pull/4374

      Attachments

        Activity

          Ascending order - Click to sort in descending order
          ajard A. Jard added a comment -

          Updating description to match the name agreed on Jep and google group discussion (from CONFIGURE to MANAGE). CONFIGURE should not be anywhere anymore.

          ajard A. Jard added a comment - Updating description to match the name agreed on Jep and google group discussion (from CONFIGURE to MANAGE). CONFIGURE should not be anywhere anymore.
          wfollonier Wadeck Follonier added a comment -

          Simpler version proposed: https://github.com/jenkinsci/jenkins/pull/4501
          (next weekly release will be 2.221)

          wfollonier Wadeck Follonier added a comment - Simpler version proposed: https://github.com/jenkinsci/jenkins/pull/4501 (next weekly release will be 2.221)

          People

            ajard A. Jard
            ajard A. Jard
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: