jenkinsci / jenkinsci/gitlab-branch-source-plugin

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

Open
#603 3 comments 0 reactions 0 assignees View on GitHub
component:gitlab-branch-source-plugin imported-jira-issue priority:major resolution:unresolved
Dominant language
Java
Stars
134
Forks
113
PR merge metrics
No merged PRs in 30d

Description

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.

---
Originally reported by justinharringa, imported from: Credentials don't seem to refresh or can't switch protocol for a server?


  • assignee: baymac
  • status: Open
  • priority: Major
  • component(s): gitlab-branch-source-plugin
  • resolution: Unresolved
  • votes: 0
  • watchers: 2
  • imported: 20251216-182730

Raw content of original issue

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.

2 attachments

- [image-2019-07-17-08-22-43-775.png](https://issues.jenkins.io/secure/attachment/48020/image-2019-07-17-08-22-43-775.png)
> ![image-2019-07-17-08-22-43-775.png](https://issues.jenkins.io/secure/attachment/48020/image-2019-07-17-08-22-43-775.png)
- [image-2019-07-17-08-23-52-586.png](https://issues.jenkins.io/secure/attachment/48019/image-2019-07-17-08-23-52-586.png)
> ![image-2019-07-17-08-23-52-586.png](https://issues.jenkins.io/secure/attachment/48019/image-2019-07-17-08-23-52-586.png)

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.