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

Confusing credentials configuration for GitHub Server Config

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • github-plugin
    • Core 1.642.1
      GitHub Plugin versions 1.14 and 1.16

      • Create a username / password credential.
      • Go to Configure System / GitHub Plugin Configuration
      • Add a GitHub Server Config

      EB: The created credential appears in the Credentials combo.
      AB: Only none is included.

      Add a username / password credential from the "Add" button in the same GitHub Server Config

      EB: The new credential is added to the global config and appears in the combo.
      AB: The new credential is added to the global config but does not appear in the combo.

          [JENKINS-32641] Confusing credentials configuration for GitHub Server Config

          Andres Rodriguez created issue -
          Andres Rodriguez made changes -
          Description Original: * Create a username / password credential.
          * Go to Configure System / GitHub Plugin Configuration
          * Add a GitHub Server Config

          EB: The created credential appears in the {{Credentials}} combo.
          AB: Only {{-none-}} is included.

          Add a username / password credential from the "Add" button in the same GitHub Server Config

          EB: The new credential is added to the global config and appears in the combo.
          AB: The new credential is added to the global config but does not appear in the combo.           		New: * Create a username / password credential.
          * Go to Configure System / GitHub Plugin Configuration
          * Add a GitHub Server Config

          EB: The created credential appears in the {{Credentials}} combo.
          AB: Only {{none}} is included.

          Add a username / password credential from the "Add" button in the same GitHub Server Config

          EB: The new credential is added to the global config and appears in the combo.
          AB: The new credential is added to the global config but does not appear in the combo.

          Kanstantsin Shautsou added a comment -

          Have you tried to use tokens? Using login/password is strongly not recommended. For converting login/password UI has helper.

          Kanstantsin Shautsou added a comment - Have you tried to use tokens? Using login/password is strongly not recommended. For converting login/password UI has helper.

          Kirill Merkushev added a comment -

          please read the doc on wiki and help in front of creds field.
          You can use only tokens to connect to GH in this plugin.

          Also, you can automatically convert your login+password creds to token creds with help of "Manage Additional GH Actions"

          Kirill Merkushev added a comment - please read the doc on wiki and help in front of creds field. You can use only tokens to connect to GH in this plugin. Also, you can automatically convert your login+password creds to token creds with help of "Manage Additional GH Actions"
          Kirill Merkushev made changes -
          Summary Original: Unable to set credentials for GitHub Server Config New: Unable to set login+password credentials for GitHub Server Config
          Kirill Merkushev made changes -
          Resolution New: Not A Defect [ 7 ]
          Status Original: Open [ 1 ] New: Closed [ 6 ]

          Andres Rodriguez added a comment -

          Hi!,

          I'm using username / password using a GitHub Personal Access Token instead of the password. With the PAT included in a "Secret Text" credential it works.
          Is this the intended behavior? That is username / password (even if not using the password) is not only not recommended but not supported?

          Thanks!

          Andres Rodriguez added a comment - Hi!, I'm using username / password using a GitHub Personal Access Token instead of the password. With the PAT included in a "Secret Text" credential it works. Is this the intended behavior? That is username / password (even if not using the password) is not only not recommended but not supported? Thanks!

          Kirill Merkushev added a comment -

          Yep, it uses oauth to talk with GH, not the basic auth, so only token is supported.

          Basic auth can be used only to create new token.

          Kirill Merkushev added a comment - Yep, it uses oauth to talk with GH, not the basic auth, so only token is supported. Basic auth can be used only to create new token.
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 168299 ] New: JNJira + In-Review [ 209649 ]

          Sorin Sbarnea added a comment -

          This bug should be reopen because the current behaviour is very confusing. The way tokens are used by everyone is that they are used instead of passwords.

          Still, even after adding github credentials into jenkins (users, and token as password), the ui does not list them and does not give any indication why. The result is a very poor user experience.

          Sorin Sbarnea added a comment - This bug should be reopen because the current behaviour is very confusing. The way tokens are used by everyone is that they are used instead of passwords. Still, even after adding github credentials into jenkins (users, and token as password), the ui does not list them and does not give any indication why. The result is a very poor user experience.
          Sorin Sbarnea made changes -
          Resolution Original: Not A Defect [ 7 ]
          Status Original: Closed [ 6 ] New: Reopened [ 4 ]

            lanwen Kirill Merkushev
            andresrc Andres Rodriguez
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: