Add support for Bearer Token Authentication #62
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When Jenkins is running on top of OpenShift, bearer token authentication is used for all REST API calls.
This means the API requests are authenticated via a header like:
Authorization: Bearer <Kubernetes/OpenShift Token>
I've been using these modifications to the plugin to trigger remote jobs on a master deployed on OpenShift with the OpenShift authentication enabled.
Example usage in a pipeline: