[JIRA] (JENKINS-49717) no token field in Openshift OAuth token credential type

20 views
Skip to first unread message

bernat.bautista@axa-groupsolutions.com (JIRA)

unread,
Feb 23, 2018, 7:38:02 AM2/23/18
to jenkinsc...@googlegroups.com
Bernat Bautista created an issue
 
Jenkins / Bug JENKINS-49717
no token field in Openshift OAuth token credential type
Issue Type: Bug Bug
Assignee: Stephen Connolly
Components: credentials-plugin
Created: 2018-02-23 12:37
Priority: Major Major
Reporter: Bernat Bautista

Hello,

 

I'm using a Jenkins master docker image based on  openshift/jenkins-2-centos7

 

I want to add a Openshift OAuth token credential, but there is no token, ID neither description field.

 

Only the Scope field is showed.

 

What can I check to see what is happening?

 

Thanks!
Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
Atlassian logo

bernat.bautista@axa-groupsolutions.com (JIRA)

unread,
Feb 23, 2018, 7:39:02 AM2/23/18
to jenkinsc...@googlegroups.com
Bernat Bautista updated an issue
Change By: Bernat Bautista
Hello,

 

I'm using a Jenkins 2.89 master docker image based on  openshift/jenkins-2-centos7


 

I want to add a Openshift OAuth token credential, but there is no token, ID neither description field.

 

Only the Scope field is showed.

 

What can I check to see what is happening?

 

Thanks!

bernat.bautista@axa-groupsolutions.com (JIRA)

unread,
Feb 23, 2018, 7:44:01 AM2/23/18
to jenkinsc...@googlegroups.com
Bernat Bautista updated an issue
Hello,

 

I'm using a Jenkins 2.89 master docker image based on  openshift/jenkins-2-centos7

 

I want to add a Openshift OAuth token credential (to configure then slaves) , but there is no token, ID neither description field.


 

Only the Scope field is showed.

 

What can I check to see what is happening?

 

Thanks!

bernat.bautista@axa-groupsolutions.com (JIRA)

unread,
Mar 22, 2018, 6:35:02 AM3/22/18
to jenkinsc...@googlegroups.com
Bernat Bautista commented on Bug JENKINS-49717
 
Re: no token field in Openshift OAuth token credential type

Any news about this issue?

 

I can imagine that openshift-login plugin is managing the OAuth token. I've tried several versions but no luck.

kurktchiev@gmail.com (JIRA)

unread,
Apr 5, 2018, 6:39:01 PM4/5/18
to jenkinsc...@googlegroups.com

I am experiencing the exact same thing, any time I try to put in an OAuth token I do not see any of the fields

jonathankuleff+jenkins@gmail.com (JIRA)

unread,
Aug 15, 2018, 12:00:02 PM8/15/18
to jenkinsc...@googlegroups.com

I am experience this issue as well
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)

jonathankuleff+jenkins@gmail.com (JIRA)

unread,
Aug 15, 2018, 12:30:03 PM8/15/18
to jenkinsc...@googlegroups.com

you can easily reproduce this but running the docker version of jenkins and installing the kubernetes plugin.

docker run -u root -d -p 8080:8080 jenkinsci/blueocean

after restarting jenkins after installing the plugin, try to create an 'OpenShift OAuth Token' credential.

there will only be scope drop down visible, no input for the token, id, etc

kim.christiansen99@gmail.com (JIRA)

unread,
Sep 20, 2018, 4:42:02 AM9/20/18
to jenkinsc...@googlegroups.com
Kim C commented on Bug JENKINS-49717

I encountered the same problem though it seems to be related to kubernetes plugin. Downgrading plugin to 1.1.4 will make input fields visible again. Issue reappear from 1.2. My current Jenkins version prevents my from testing if this is solved in latest version.
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

kim.christiansen99@gmail.com (JIRA)

unread,
Sep 20, 2018, 4:43:02 AM9/20/18
to jenkinsc...@googlegroups.com
Kim C updated an issue
 
Change By: Kim C
Component/s: kubernetes-plugin
Component/s: credentials-plugin

stephen.alan.connolly@gmail.com (JIRA)

unread,
Oct 31, 2018, 6:00:27 AM10/31/18
to jenkinsc...@googlegroups.com
Stephen Connolly assigned an issue to Unassigned
 

Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA
Change By: Stephen Connolly
Assignee: Stephen Connolly

lynchseanm@gmail.com (JIRA)

unread,
Jan 9, 2019, 4:32:04 PM1/9/19
to jenkinsc...@googlegroups.com
Sean Lynch commented on Bug JENKINS-49717
 
Re: no token field in Openshift OAuth token credential type

As a workaround until this is fixed, I went in and manually edited credentials.xml. Here are the steps.

First, go and create the Openshift OAuth token (hit OK even though it didn't give you any place to add the actual token).

Next, open up credentials.xml and find the entry for the newly created token:

<org.csanchez.jenkins.plugins.kubernetes.OpenShiftTokenCredentialImpl>

...

</org.csanchez.jenkins.plugins.kubernetes.OpenShiftTokenCredentialImpl>

The description field will be blank and you can add one here. Then add a tag for <secret></secret> and put the token in there.

Finally restart Jenkins.

aburdajewicz@cloudbees.com (JIRA)

unread,
Jul 2, 2019, 10:33:02 PM7/2/19
to jenkinsc...@googlegroups.com

aburdajewicz@cloudbees.com (JIRA)

unread,
Jul 2, 2019, 10:45:03 PM7/2/19
to jenkinsc...@googlegroups.com

Those credentials types have been moved from the kubernetes plugin to kubernetes credentials but partially.

The "Openshift OAuth token" we see in the dropdown is the deprecated https://github.com/jenkinsci/kubernetes-plugin/blob/kubernetes-1.16.3/src/main/java/org/csanchez/jenkins/plugins/kubernetes/OpenShiftTokenCredentialImpl.java that has no specific jelly for it so we see the bare minimum in the UI. If you install Kubernetes Credentials plugin but not the Kubernetes Plugin, you will see only the "Openshift Username and Password" option.

aburdajewicz@cloudbees.com (JIRA)

unread,
Jul 2, 2019, 10:45:04 PM7/2/19
to jenkinsc...@googlegroups.com
Allan BURDAJEWICZ edited a comment on Bug JENKINS-49717
Those credentials types have been moved from the kubernetes plugin to kubernetes credentials but partially.



The "Openshift OAuth token" we see in the dropdown is the deprecated https://github.com/jenkinsci/kubernetes-plugin/blob/kubernetes-1.16.3/src/main/java/org/csanchez/jenkins/plugins/kubernetes/OpenShiftTokenCredentialImpl.java that has no specific jelly for it so we see the bare minimum in the UI. If you install Kubernetes Credentials plugin but not the Kubernetes Plugin, you will see only the "Openshift Username and Password" option.

aburdajewicz@cloudbees.com (JIRA)

unread,
Jul 2, 2019, 10:51:33 PM7/2/19
to jenkinsc...@googlegroups.com

As Carlos Sanchez mentioned in https://github.com/jenkinsci/kubernetes-credentials-plugin/pull/2, the Open Shift Token Credentials is not needed anymore as it is the same as a StringCredentials (Secret Text) and the kubernetes plugin now supports it.

aburdajewicz@cloudbees.com (JIRA)

unread,
Jul 3, 2019, 12:14:04 AM7/3/19
to jenkinsc...@googlegroups.com
Allan BURDAJEWICZ assigned an issue to Allan BURDAJEWICZ
 
Change By: Allan BURDAJEWICZ
Assignee: Allan BURDAJEWICZ

aburdajewicz@cloudbees.com (JIRA)

unread,
Jul 3, 2019, 12:14:05 AM7/3/19
to jenkinsc...@googlegroups.com
Allan BURDAJEWICZ started work on Bug JENKINS-49717
 
Change By: Allan BURDAJEWICZ
Status: Open In Progress

aburdajewicz@cloudbees.com (JIRA)

unread,
Jul 3, 2019, 12:15:03 AM7/3/19
to jenkinsc...@googlegroups.com
Change By: Allan BURDAJEWICZ
Status: In Progress Review

vincent@latombe.net (JIRA)

unread,
Jul 3, 2019, 3:40:03 AM7/3/19
to jenkinsc...@googlegroups.com
Change By: Vincent Latombe
Status: In Review Fixed but Unreleased
Resolution: Fixed

jglick@cloudbees.com (JIRA)

unread,
Jul 8, 2019, 2:50:03 PM7/8/19
to jenkinsc...@googlegroups.com
Change By: Jesse Glick
Status: Fixed but Unreleased Resolved

jglick@cloudbees.com (JIRA)

unread,
Jul 8, 2019, 2:51:03 PM7/8/19
to jenkinsc...@googlegroups.com
Jesse Glick updated an issue
Change By: Jesse Glick
Released As: 1.16.4
Reply all
Reply to author
Forward
0 new messages