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

Allow Credentials for Build Auth to be personal access token or generic SSH access key

XMLWordPrintable

      Since regular credentials expire and service accounts take up Bitbucket license seats, it would be ideal if this plugin better supported generic SSH access keys, or at the very least accepted a personal access token for the "Credentials (for build auth)" field.

      SSH access keys work in the "Optional SSH Credentials" field today if you leave the "Credentials (for build auth)" field empty and copy/paste your project and repo names in, but of course you lose the autocomplete functionality.

          [JENKINS-66208] Allow Credentials for Build Auth to be personal access token or generic SSH access key

          Martin Henschke added a comment - - edited

          Hi Stephen, thanks for your comment.

          I'm thinking about this ticket in two parts- permit SSH access keys to be used instead of username password credentials, and permitting token credentials to be used instead of username password credentials.
          The former issue has been reported under JENKINS-65466, so you can follow that ticket for more information.
          For token credentials, our SCM wraps the git plugin, which does not have support for our custom credential type so this is unlikely to be done. You can use personal access tokens for cloning however- create a new username-password credential in Jenkins, using the username of the account as the username, and the access token as the password. This allows you to use a personal access token without (hopefully) requiring a service account.

          I will mark this as a dupe, but hopefully that gives you an option in the meantime.

          Martin Henschke added a comment - - edited Hi Stephen, thanks for your comment. I'm thinking about this ticket in two parts- permit SSH access keys to be used instead of username password credentials, and permitting token credentials to be used instead of username password credentials. The former issue has been reported under JENKINS-65466 , so you can follow that ticket for more information. For token credentials, our SCM wraps the git plugin, which does not have support for our custom credential type so this is unlikely to be done. You can use personal access tokens for cloning however- create a new username-password credential in Jenkins, using the username of the account as the username, and the access token as the password. This allows you to use a personal access token without (hopefully) requiring a service account. I will mark this as a dupe, but hopefully that gives you an option in the meantime.

            Unassigned Unassigned
            shodgson11 Stephen Hodgson
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: