Hi there,

      I am finding that no matter what I do. I do not have any credentials to select from the dropdown:



      I have added the credentials to the Github plugin in the Jenkins General Config and under the Github Pull Request Builder.

      Attached is the versions of all of the Github Plugins I am using:

      Using Jenkins 2.26.

      Am I doing something wrong?

      This is not resolved by disabling CSRF Crumbs, and I am using NGINX, already looked over JENKINS-12875.

          [JENKINS-39086] Scan Credentials dropdown is always empty

          Drew Easley added a comment -

          Can you try manually adding a GitHub username/password to the Jenkins credentials list? You can use a GitHub "personal access token" for the password. The "scan credentials" list seems to filter certain types of credentials (like SSH keys) out of the drop down list.

          Drew Easley added a comment - Can you try manually adding a GitHub username/password to the Jenkins credentials list? You can use a GitHub "personal access token" for the password. The "scan credentials" list seems to filter certain types of credentials (like SSH keys) out of the drop down list.

          Greg Parsons added a comment -

          I manually added keys from the credentials page for the scope "global credentials unrestricted" and they do not shown up in the plugin.

          Attaching images

          Greg Parsons added a comment - I manually added keys from the credentials page for the scope "global credentials unrestricted" and they do not shown up in the plugin. Attaching images

          Drew Easley added a comment -

          Can you let me know if the drop down box is properly populated if you add a credential with the type "username and password" instead of the "secret text" type?

          Drew Easley added a comment - Can you let me know if the drop down box is properly populated if you add a credential with the type "username and password" instead of the "secret text" type?

          Did you try creating username/password credentials? (the password can be the token)

          Stephen Connolly added a comment - Did you try creating username/password credentials? (the password can be the token)

          Same issue. Re-creating the credential as username/password worked. But it's very confusing ...

          Felix Geisendörfer added a comment - Same issue. Re-creating the credential as username/password worked. But it's very confusing ...

          The Add button cannot currently be provided with the context to know what credential types are accepted by the select drop down.

          Thus when you add credentials, there is nothing stopping you from adding an irrelevant type of credentials or even adding an irrelevant type into a credential domain that will not be matched.

          The best that we can do is to prevent the select drop down from allowing you to select invalid credentials

          Stephen Connolly added a comment - The Add button cannot currently be provided with the context to know what credential types are accepted by the select drop down. Thus when you add credentials, there is nothing stopping you from adding an irrelevant type of credentials or even adding an irrelevant type into a credential domain that will not be matched. The best that we can do is to prevent the select drop down from allowing you to select invalid credentials

          This is a duplicate of JENKINS-40293

          Stephen Connolly added a comment - This is a duplicate of JENKINS-40293

            Unassigned Unassigned
            gregorskii Greg Parsons
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: