Details
-
Type:
New Feature
-
Status: Closed (View Workflow)
-
Priority:
Minor
-
Resolution: Not A Defect
-
Component/s: github-api-plugin, github-branch-source-plugin, github-plugin
-
Labels:None
-
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
Issue Links
- relates to
-
JENKINS-57351 Support for making Jenkins a "GitHub App"
-
- Resolved
-
Github is removing all support for basic auth on Nov 13, 2020 (with service brownouts on Sep 30 and Oct 28)
https://developer.github.com/changes/2020-02-14-deprecating-password-auth/
I have been using an access token with the "Username with password" credential type, but I don't think this will continue to work, as the branch source plugin is still sending those credentials via basic auth:
https://github.com/jenkinsci/github-branch-source-plugin/blob/9d1f48ec47eb5d44f668936d0811a6715fcc6f35/src/main/java/org/jenkinsci/plugins/github_branch_source/Connector.java#L406
https://github.com/github-api/github-api/blob/5c9474d1c891121f11ce9c31b51d42216a8e416f/src/main/java/org/kohsuke/github/GitHubClient.java#L119-L123
Is the branch source plugin currently capable of sending the credentials via the HTTP Authorization header, or will this require a code change?