-
New Feature
-
Resolution: Unresolved
-
Minor
-
None
I would like to use the built-in jenkins-cli for our automation towards Jenkins.
However, we are using the Openshift OAuth login integration. For this to work, we need to use the Openshift token as Bearer to be able to login, but jenkins-cli always creates Basic value in the auth header.
I.e. we would like to do something as the following ("oc" is the Openshift client):
oc login https://ose-console.cluster TOKEN=$(oc whoami -t) JENKINS_URL=https://jenkins.in.ose.cluster java -jar jenkins-cli.jar -auth $TOKEN help build
[JENKINS-61965] Support for Bearer token in jenkins-cli
Soren A D
created issue -
Soren A D
made changes -
| Description |
Original:
I would like to use the built-in jenkins-cli for our automation towards Jenkins. However, we are using the Openshift OAuth login integration. For this to work, we need to use the Openshift token as Bearer to be able to login. |
New:
I would like to use the built-in jenkins-cli for our automation towards Jenkins. However, we are using the Openshift OAuth login integration. For this to work, we need to use the Openshift token as Bearer to be able to login, but jenkins-cli always creates Basic value in the auth header. |
Soren A D
made changes -
| Description |
Original:
I would like to use the built-in jenkins-cli for our automation towards Jenkins. However, we are using the Openshift OAuth login integration. For this to work, we need to use the Openshift token as Bearer to be able to login, but jenkins-cli always creates Basic value in the auth header. |
New:
I would like to use the built-in jenkins-cli for our automation towards Jenkins. However, we are using the Openshift OAuth login integration. For this to work, we need to use the Openshift token as Bearer to be able to login, but jenkins-cli always creates Basic value in the auth header. E.g. we would like to do something as the following ("oc" is the Openshift client): {noformat} oc login https://ose-console.cluster TOKEN=$(oc whoami -t) JENKINS_URL=https://jenkins.in.ose.cluster java -jar jenkins-cli.jar -auth $TOKEN help build {noformat} |
Soren A D
made changes -
| Description |
Original:
I would like to use the built-in jenkins-cli for our automation towards Jenkins. However, we are using the Openshift OAuth login integration. For this to work, we need to use the Openshift token as Bearer to be able to login, but jenkins-cli always creates Basic value in the auth header. E.g. we would like to do something as the following ("oc" is the Openshift client): {noformat} oc login https://ose-console.cluster TOKEN=$(oc whoami -t) JENKINS_URL=https://jenkins.in.ose.cluster java -jar jenkins-cli.jar -auth $TOKEN help build {noformat} |
New:
I would like to use the built-in jenkins-cli for our automation towards Jenkins. However, we are using the Openshift OAuth login integration. For this to work, we need to use the Openshift token as Bearer to be able to login, but jenkins-cli always creates Basic value in the auth header. I.e. we would like to do something as the following ("oc" is the Openshift client): {noformat} oc login https://ose-console.cluster TOKEN=$(oc whoami -t) JENKINS_URL=https://jenkins.in.ose.cluster java -jar jenkins-cli.jar -auth $TOKEN help build {noformat} |