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

github is deprecating basic authentication using password

    Details

    • Similar Issues:

      Description

      You recently used a password to access an endpoint through the GitHub API using okhttp/2.7.5. We will deprecate basic authentication using password to this endpoint soon:

      https://api.github.com/repositories/155774655

      We recommend using a personal access token (PAT) with the appropriate scope to access this endpoint instead. Visit https://github.com/settings/tokens for more information.

      This might be just something that admins need to deal w/, but it would be helpful if there was a migration page explaining what to do from the jenkins side.

      (it isn't particularly obvious to me)

        Attachments

          Activity

          Hide
          jenkinscr Carlos Jenkins added a comment -

          Hi,

          I got the same email for two of my Jenkins deployments. That's how I got here

          In particular the GitHub Branch Source Plugin only supports using username and password, so the functionality provided by that plugin may break when the deprecation takes place.

          Current code of the GitHub Branch Source Plugin shows:

          https://github.com/jenkinsci/github-branch-source-plugin/blob/23c8a226eef074da7b87bc4b629f6a9f75bf4766/src/main/java/org/jenkinsci/plugins/github_branch_source/Connector.java#L339

           

          Looking at what PyGitHub does (project that I use with tokens to automate some things):

          https://github.com/PyGithub/PyGithub/blob/baddb7193f24fc988def1ead53876024be6066e0/github/Requester.py#L278

           

           

          It looks like GitHub supports passing token in the Authorization header. So, in theory, the GitHub Branch Source Plugin could use a "Secret Text" type secret with the token an pass it down in the Authorization header.

          Its interesting to note that the GitHub Plugin already supports (actually only supports) using access tokens. So, in my Jenkins deployment I have to have two secrets:

          • A "Username with password" type for GitHub Branch Source Plugin, and
          • A "Secret text" for the GitHub plugin.

           

           

          Show
          jenkinscr Carlos Jenkins added a comment - Hi, I got the same email for two of my Jenkins deployments. That's how I got here In particular the GitHub Branch Source Plugin only supports using username and password, so the functionality provided by that plugin may break when the deprecation takes place. Current code of the GitHub Branch Source Plugin shows: https://github.com/jenkinsci/github-branch-source-plugin/blob/23c8a226eef074da7b87bc4b629f6a9f75bf4766/src/main/java/org/jenkinsci/plugins/github_branch_source/Connector.java#L339   Looking at what PyGitHub does (project that I use with tokens to automate some things): https://github.com/PyGithub/PyGithub/blob/baddb7193f24fc988def1ead53876024be6066e0/github/Requester.py#L278     It looks like GitHub supports passing token in the Authorization header. So, in theory, the GitHub Branch Source Plugin could use a "Secret Text" type secret with the token an pass it down in the Authorization header. Its interesting to note that the GitHub Plugin already supports (actually only supports) using access tokens. So, in my Jenkins deployment I have to have two secrets: A "Username with password" type for GitHub Branch Source Plugin, and A "Secret text" for the GitHub plugin.    
          Hide
          markewaite Mark Waite added a comment -

          Isn't that message saying that you can continue to use basic auth so long as instead of using your actual password you use a personal access token. Generate a personal access token from the GitHub "Settings" page and store that personal access token in the Jenkins username / password credential as the password. Place your username as the username. Check that it works. It has been working that way for me.

          Show
          markewaite Mark Waite added a comment - Isn't that message saying that you can continue to use basic auth so long as instead of using your actual password you use a personal access token. Generate a personal access token from the GitHub "Settings" page and store that personal access token in the Jenkins username / password credential as the password. Place your username as the username. Check that it works. It has been working that way for me.
          Hide
          jsoref Josh Soref added a comment -

          Mark Waite: Do you know what permissions we should give it in https://github.com/settings/tokens/new?

          My ticket isn't claiming that work necessarily needs to be done in the plugin, just that a "what to do" should be published. (Although, probably it's best for the plugin to just guide people through the process since it seems like it'd be pretty easy for it to do that and remember "this token is good" or something.)

          Show
          jsoref Josh Soref added a comment - Mark Waite : Do you know what permissions we should give it in  https://github.com/settings/tokens/new ? My ticket isn't claiming that work necessarily needs to be done in the plugin, just that a "what to do" should be published. (Although, probably it's best for the plugin to just guide people through the process since it seems like it'd be pretty easy for it to do that and remember "this token is good" or something.)
          Hide
          markewaite Mark Waite added a comment - - edited

          Repository read should be enough Josh Soref, unless your job is pushing changes back to the server.

          I think we should document the credential choices as part of a larger picture of ways to use Jenkins most effectively with git. When using GitHub, prefer username and a personal access tokens rather than username and password. Same advice would apply to Bitbucket, Gitlab, Gitea, Team Foundation Server, and more.

          Show
          markewaite Mark Waite added a comment - - edited Repository read should be enough Josh Soref , unless your job is pushing changes back to the server. I think we should document the credential choices as part of a larger picture of ways to use Jenkins most effectively with git. When using GitHub, prefer username and a personal access tokens rather than username and password. Same advice would apply to Bitbucket, Gitlab, Gitea, Team Foundation Server, and more.
          Hide
          jsoref Josh Soref added a comment -

          Also, a quick look at my jenkins /credentials/store/system/domain/_/ shows that the account currently has a token with repo which was Last used within the last week according to github, and yet, I'm still getting warnings.

          Show
          jsoref Josh Soref added a comment - Also, a quick look at my jenkins /credentials/store/system/domain/_/  shows that the account currently has a token with repo which was Last used within the last week according to github, and yet, I'm still getting warnings.
          Hide
          markewaite Mark Waite added a comment -

          Maybe you're using the actual password from another location or through a different credential? I've not received any warnings from GitHub for my https repository access. I'll continue watching my mailbox in case it arrives.

          Show
          markewaite Mark Waite added a comment - Maybe you're using the actual password from another location or through a different credential? I've not received any warnings from GitHub for my https repository access. I'll continue watching my mailbox in case it arrives.
          Hide
          jsoref Josh Soref added a comment - - edited

          Ok, for us, there were apparently two items. I've switched things over to the other one. Hopefully that will make the alert go away.

          But this experience was painful.

          One thing that would help immensely is the ability to search for credentials whose password matches an entered value. Expected results should only include passwords the searching user is allowed to use. Had I been able to do that, I could have quickly identified the problem.

          Fwiw, the best I've managed is:

          admin:org, admin:public_key, admin:repo_hook, read:user, repo 

          We had credentials of:

          repo 
          admin:repo_hook, repo 

          But they weren't sufficient for us.

          Show
          jsoref Josh Soref added a comment - - edited Ok, for us, there were apparently two items. I've switched things over to the other one. Hopefully that will make the alert go away. But this experience was painful. One thing that would help immensely is the ability to search for credentials whose password matches an entered value. Expected results should only include passwords the searching user is allowed to use. Had I been able to do that, I could have quickly identified the problem. Fwiw, the best I've managed is: admin:org, admin:public_key, admin:repo_hook, read:user, repo We had credentials of: repo admin:repo_hook, repo But they weren't sufficient for us.
          Hide
          albertski Albert Jankowski added a comment - - edited

          Mark Waite I did the following:

          • Created personal token in Github
          • Created credentials in Jenkins: username is username and password is the Github token
          • Now I navigate to Manage Jenkins -> Configure System -> Github
          • Under credentials, I don't see the new credentials I created in one of the previous steps (I'm guessing because it was username and password and it only shows items with keys only)

          Also, I did try:

          • Advance -> Manage Additional Github Actions -> Convert login and password to token
          • When I create the token from the credentials I get the following error:
            Can't create GH token - {"message":"This API can only be accessed with username and password Basic Auth","documentation_url":"https://developer.github.com/v3"}
            
          • When I create token from login and password (username = username, password = token) I get:
            Can't create GH token for xenomedia-deploy - {"message":"This API can only be accessed with username and password Basic Auth","documentation_url":"https://developer.github.com/v3"}
            
          • When I create token from login and password (actual username and password)
            Can't create GH token for username - null
            

          Any idea what I am doing wrong? You mentioned that this was working for you.

          Show
          albertski Albert Jankowski added a comment - - edited Mark Waite I did the following: Created personal token in Github Created credentials in Jenkins: username is username and password is the Github token Now I navigate to Manage Jenkins -> Configure System -> Github Under credentials, I don't see the new credentials I created in one of the previous steps (I'm guessing because it was username and password and it only shows items with keys only) Also, I did try: Advance -> Manage Additional Github Actions -> Convert login and password to token When I create the token from the credentials I get the following error: Can't create GH token - { "message" : "This API can only be accessed with username and password Basic Auth" , "documentation_url" : "https: //developer.github.com/v3" } When I create token from login and password (username = username, password = token) I get: Can't create GH token for xenomedia-deploy - { "message" : "This API can only be accessed with username and password Basic Auth" , "documentation_url" : "https: //developer.github.com/v3" } When I create token from login and password (actual username and password) Can't create GH token for username - null Any idea what I am doing wrong? You mentioned that this was working for you.
          Hide
          markewaite Mark Waite added a comment - - edited

          Albert Jankowski the technique that works on my Jenkins server is to use the GitHub personal access token to define a Secret text credential, then use that in the Manage Jenkins -> GitHub section. I was personally surprised when that worked, since I've been conditioned to use one of two types of credentials to interact with GitHub, either private key (for ssh protocol) or username/password (for https). Secret text is a third type and that "Manage Jenkins" field for GitHub is the only place where I've used it as far as I remember.

          Show
          markewaite Mark Waite added a comment - - edited Albert Jankowski the technique that works on my Jenkins server is to use the GitHub personal access token to define a Secret text credential, then use that in the Manage Jenkins -> GitHub section. I was personally surprised when that worked, since I've been conditioned to use one of two types of credentials to interact with GitHub, either private key (for ssh protocol) or username/password (for https). Secret text is a third type and that "Manage Jenkins" field for GitHub is the only place where I've used it as far as I remember.
          Hide
          albertski Albert Jankowski added a comment -

          Thanks Mark Waite. Adding just the personal access token as Secret Text did work. I'll see if I get an alert of deprecated authentication.

          Show
          albertski Albert Jankowski added a comment - Thanks Mark Waite . Adding just the personal access token as Secret Text did work. I'll see if I get an alert of deprecated authentication.

            People

            • Assignee:
              lanwen Kirill Merkushev
              Reporter:
              jsoref Josh Soref
            • Votes:
              2 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

              • Created:
                Updated: