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

User Scoped credentials don't appear in credentials drop down lists

      Environment

      • Jenkins 2.46.2
      • credentials:2.1.13 'Credentials Plugin'
      • credentials-binding:1.11 'Credentials Binding Plugin'
      • workflow-aggregator:2.5 'Pipeline'
      • workflow-api:2.12 'Pipeline: API'
      • workflow-basic-steps:2.4 'Pipeline: Basic Steps'
      • workflow-cps:2.29 'Pipeline: Groovy'
      • workflow-cps-checkpoint:2.4 'CloudBees Pipeline: Groovy Checkpoint Plugin'
      • workflow-cps-global-lib:2.7 'Pipeline: Shared Groovy Libraries'
      • workflow-durable-task-step:2.10 'Pipeline: Nodes and Processes'
      • workflow-job:2.10 'Pipeline: Job'
      • workflow-multibranch:2.14 'Pipeline: Multibranch'
      • workflow-scm-step:2.4 'Pipeline: SCM Step'
      • workflow-step-api:2.9 'Pipeline: Step API'
      • workflow-support:2.14 'Pipeline: Supporting APIs'

      Scenario to Use User Scoped Credentials in "withCredentials()"

      Many organizations use GPG signing keys and special permissions on Git / Nexus / Artifactory to create releases. For traceability and security, these privileged credentials credentials are "per individual/personal credentials", they are not shared with team members.

      For this kind of credentials, we want to use Jenkins User Scoped Credentials in pipeline (withCredentials, git, config-file-provider, ssh-agent...)

      Description

      • Even when using the authorize project plugin, user Scoped Credentials don't appear in the drop down lists of credentials.
      • User scoped credentials don't appear in the drop down lists of credentials of the "Config File Provider Plugin" (problem not covered by this jira issue, I'll work on it later)

      Reproduce

      • Install the Project Authorize Plugin and configure it "Run as user who triggered the build"
      • Create user scoped credentials "my-username-password"
      • Create a pipeline
      • Use the pipeline syntax assistant to generate a "withCredentials" wrapper
      • The drop down list of credentials don't display the user scoped credentials "my-username-password"

          [JENKINS-44774] User Scoped credentials don't appear in credentials drop down lists

          Cyrille Le Clerc created issue -
          Cyrille Le Clerc made changes -
          Link New: This issue is related to JENKINS-44772 [ JENKINS-44772 ]
          Cyrille Le Clerc made changes -
          Link New: This issue is related to JENKINS-44773 [ JENKINS-44773 ]

          John Zerbe added a comment -

          should be "blocker"

          John Zerbe added a comment - should be "blocker"
          Cyrille Le Clerc made changes -
          Priority Original: Minor [ 4 ] New: Major [ 3 ]

          Cyrille Le Clerc added a comment - - edited

          FYI the reasoning why xjg6yzl feels it's a "blocker" are also detailed on

          xjg6yzl I changed the priority of this issue to "major" for the moment. I'll let the community discussion help us define how important it is. I share your opinion that it's a very important feature but I don't want to interfere with the thought process of the community

          Cyrille Le Clerc added a comment - - edited FYI the reasoning why xjg6yzl feels it's a "blocker" are also detailed on https://issues.jenkins-ci.org/browse/JENKINS-44772?focusedCommentId=302524&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-302524 https://issues.jenkins-ci.org/browse/JENKINS-44773?focusedCommentId=302534&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-302534 xjg6yzl I changed the priority of this issue to "major" for the moment. I'll let the community discussion help us define how important it is. I share your opinion that it's a very important feature but I don't want to interfere with the thought process of the community

          John Zerbe added a comment -

          cleclerc, Thank you for this change in in priority. To reiterate, we have auditing requirements to show exactly who did every single push to our git repositories. We currently do this via more traditional Jenkins maven type jobs and maven steps in freeform jobs where we use the maven release plugin combined with user scoped credentials to allow maven to create the tags and update the version via an individual's credentials picked at build time.  We do set security at the folder level for teams, but using credentials at the folder scope does not meet our requirements. 

          John Zerbe added a comment - cleclerc , Thank you for this change in in priority. To reiterate, we have auditing requirements to show exactly who did every single push to our git repositories. We currently do this via more traditional Jenkins maven type jobs and maven steps in freeform jobs where we use the maven release plugin combined with user scoped credentials to allow maven to create the tags and update the version via an individual's credentials picked at build time.  We do set security at the folder level for teams, but using credentials at the folder scope does not meet our requirements. 

          Thanks xjg6yzl for the details.

          Cyrille Le Clerc added a comment - Thanks xjg6yzl for the details.

          Jesse Glick added a comment -

          Ignoring

          • User scoped credentials don't appear in the drop down lists of credentials of the "Config File Provider Plugin"

          which is not part of the steps to reproduce. Typo?

          Jesse Glick added a comment - Ignoring User scoped credentials don't appear in the drop down lists of credentials of the "Config File Provider Plugin" which is not part of the steps to reproduce. Typo?
          Jesse Glick made changes -
          Component/s New: credentials-binding-plugin [ 18129 ]
          Component/s Original: credentials-plugin [ 16523 ]
          Assignee Original: Stephen Connolly [ stephenconnolly ]

            Unassigned Unassigned
            cleclerc Cyrille Le Clerc
            Votes:
            5 Vote for this issue
            Watchers:
            12 Start watching this issue

              Created:
              Updated:
              Resolved: