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

UX: non-obvious that API tokens need to be stored as UsernamePassword to work as scan credentials

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      The drop down dialog to select github org scan credentials only lists `UsernamePasswordCredentialsImpl` credentials. While the `github` plugin also supports `StringCredentialsImpl` credentials – I found this rather confusing as I only use github API tokens. I have a preference for using API tokens with robots as it is somewhat easier to revoke access.

        Attachments

          Issue Links

            Activity

            jhoblitt Joshua Hoblitt created issue -
            jhoblitt Joshua Hoblitt made changes -
            Field Original Value New Value
            Summary API tokens not supported as scan credential API tokens not supported as scan credentials
            stephenconnolly Stephen Connolly made changes -
            Link This issue is related to JENKINS-33228 [ JENKINS-33228 ]
            stephenconnolly Stephen Connolly made changes -
            Summary API tokens not supported as scan credentials UX: non-obvious that API tokens need to be stored as UsernamePassword to work as scan credentials

              People

              Assignee:
              kohsuke Kohsuke Kawaguchi
              Reporter:
              jhoblitt Joshua Hoblitt
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated: