[JIRA] (JENKINS-58532) Credentials don't seem to refresh or can't switch protocol for a server?

[justin@harringa.com (JIRA)]

Justin Harringa created an issue

Jenkins / JENKINS-58532 Credentials don't seem to refresh or can't switch protocol for a server? Issue Type: Bug Assignee: Parichay Barpanda Attachments: image-2019-07-17-08-22-43-775.png, image-2019-07-17-08-23-52-586.png Components: gitlab-branch-source-plugin Created: 2019-07-17 15:24 Priority: Major Reporter: Justin Harringa I had originally started out using a single GitLab server configuration in Manage Jenkins with an SSH Key. I then tried to add a new GitLab Personal Access Token from within the job creation screen and it didn't show up after hitting Save. Next, I tried to create a GitLab Personal Access Token from the main Credentials screen. It still did not show up in the job configuration.    I can see all of the credentials in the Credentials plugin screens. However, it appears that the GitLab configuration only wants to show the SSH Key credential. Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

[justin@harringa.com (JIRA)]

Justin Harringa updated an issue

Jenkins / JENKINS-58532 Credentials don't seem to refresh or can't switch protocol for a server?

Change By: Justin Harringa

I had originally started out using a single GitLab server configuration in Manage Jenkins with an SSH Key. I then tried to add a new GitLab Personal Access Token from within the job creation screen and it didn't show up after hitting Save. Next, I tried to create a GitLab Personal Access Token from the main Credentials screen. It still did not show up in the job configuration.

I can see all of the credentials in the Credentials plugin screens. However, it appears that the GitLab configuration only wants to show the SSH Key credential. Perhaps the server configuration somehow gets locked to a protocol? If that's the case, that might not be great from a security perspective since it would seem that job configuration might affect the whole Jenkins server configuration. !image-2019-07-17-08-22-43-775.png! !image-2019-07-17-08-23-52-586.png!

Add Comment

[parichay.barpanda@gmail.com (JIRA)]

Parichay Barpanda commented on JENKINS-58532

Re: Credentials don't seem to refresh or can't switch protocol for a server? Justin Harringa In GitLab Server Configuration, you need to add `GitLab Personal Access Token` because the API can be accessed via the token. If you add SSH Key in GitLab Server configuration, it shouldn't show up as only the `GitLab Personal Access Token` type credentials are matched. In the Job configuration, you need to add the checkout credential which can only be of type `SSHPrivateKey` or `UsernamePasswordCredentials`. If credential of `GitLab Personal Access Token` is added it won't show up. Please let me know if my interpretation is not what you are trying to explain here.

Add Comment

[parichay.barpanda@gmail.com (JIRA)]

Parichay Barpanda commented on JENKINS-58532

Re: Credentials don't seem to refresh or can't switch protocol for a server?

But the checkout with SSH credential is not working. That I acknowledge. Will fix it.

Add Comment