[JIRA] (JENKINS-38126) Credentials dropdown empty on git scm with specific authorize project settings

[de...@ikedam.jp (JIRA)]

Title: Message Title

ikedam updated JENKINS-38126   I tested the behavior of the combination of git-plugin, credentials-plugin and authorize-project-plugin and I believe this issue is caused for following three issues: There're three underlying issues causing this issue: Why this happens only for "Run as specific user" , not for other strategies like "Run as User who Triggered"?: Because credentials in configuration pages are not for the user of builds, but for the user of the job. Jenkins can say that the user of the job is "user1" when you are using "Run as specific user" with "user1" though Jenkins cannot decide the user of the job when you are using "Run as User who Triggered" as the user can be decided only after a build is actually triggered by someone. So "Run as User who Triggered" results configuration pages behave just as when no authorization strategy is set. And this issue is specific to "Run as specific user". What is credentials for specific users? You can configure user-scoped credentials in the user page, which can open from the link over the user name in the right-up part of Jenkins web UI. I suppose many users configures only system-scoped credentials and this results "no credentials are shown". Why system global credentials are not displayed in the job configuration pages even when the user has Credentials/View permissions? It might be a bug of credentials plugin (I'm not so sure as I don't know much about the design of credentials-plugin). I created JENKINS-58902 and please watch that ticket. The first and second ones can be resolved as "Not A Defect", as they are designated behavior. For the third one, I created JENKINS-58902. I believe this issue (JENKINS-38126) can be resolved as Duplicate, and please watch that ticket instead. Those causes are really complicated and I'm afraid they are beyond my English and difficult to read. I expect someone improve the explanation. And this ticket lasted for so long time and I might fail to get exactly what happened. Please add a comment or reopen the ticket if you have something that looks not resolved. Jenkins / JENKINS-38126 Credentials dropdown empty on git scm with specific authorize project settings Change By: ikedam Status: Open Fixed but Unreleased Assignee: Gunter Grodotzki Resolution: Duplicate Add Comment   This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.174282.1473669042000.1510.1565671501548%40Atlassian.JIRA.