Using Bearer Token Authentication for the Git plugin and Git Client Plugin
Project goal: To introduce a new authentication technique for both the Git plugin and Git Client plugin
Skills to study/improve: Java, Authentication techniques, Jenkins plugin development
NOTE:
This idea is published as a draft under active discussion, but it is confirmed in principle.
It is FINE to apply to it.
The scope and the suggested implementation may change significantly before the final version is published.
Sections like quickstart guide and newbie-friendly issues may be also missing.
As a contributor, you are welcome to request additional information and to join the discussions using channels linked on this page.
Details
Background
Currently neither the Jenkins Git plugin nor the Jenkins Git Client plugin support the use of bearer token authentication. This project would add support for bearer token authentication to both plugins.
Potential Mentors
Project Links
Organization Links
- Jenkins GSoC page - documentation, application guidelines
- Participate and contribute to Jenkins - landing page for newcomer contributors
- Newbie-friendly issues - list of organization-wide newbie-friendly issues (use them if there is no links in the project idea)
On this page
Connect
Recent Blog Posts
- Jenkins October 2023 Newsletter
- Jenkins Contributor Summit in Brussels
- Introducing the 2 + 2 + 2 Java support plan
- Back of the Napkin Guide to Updating Jenkins, for the uninitiated
- What is the plugin health score?
- Jenkins September 2023 Newsletter
- Prototype removed from Jenkins 2.426
- Supercharge Your Jenkins Workflow with Mergify
- GSoC Building Jenkins.io with alternative tools
- Incremental Build Detection Probe