[JIRA] (JENKINS-55052) Different behavior accessing user credentials using RunAs Specific vs. Triggered User

[michael.i.ah...@gmail.com (JIRA)]

Title: Message Title

Michael Ahern created an issue   Jenkins / JENKINS-55052 Different behavior accessing user credentials using RunAs Specific vs. Triggered User Issue Type: Bug Assignee: ikedam Components: authorize-project-plugin Created: 2018-12-06 12:01 Environment: Using plugin version 1.3.0 Priority: Major Reporter: Michael Ahern Using a trivial Pipeline project, we are seeing differing credential behavior with `Run As Specific User` vs `Run As User who Triggered Build` using User Private credentials (https://<server>/user/<user>/credentials/store/user/domain/_/).   Here is the code for the Pipeline. This is configured inline in the Pipeline Job. // code placeholder node { withCredentials([usernameColonPassword(credentialsId: 'user-private-credential', variable: 'SOME_VALUE')]) { sh('echo ${SOME_VALUE} | shasum') } }   In the Pipeline above `user-private-credential` is defined for the user executing the script. — When the Authorization mode is set to "Run As Specific Build", the script is able to successfully retrieve the user's credentials.   If the Authorization mode is set to "Run As User who Triggered Build", then the pipeline is unable to retrieve the credentials. —   The desired behavior is to be able to retrieve the credentials in both cases.   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. For more options, visit https://groups.google.com/d/optout.