[JIRA] (JENKINS-38963) User-scoped credentials cannot be looked up in pipeline
Title: Message Title Vít Zikmund edited a comment on JENKINS-38963 Re: User-scoped credentials cannot be looked up in pipeline Hello there, [~jvz]. If you suggest using the authorize- project plugin for this purpose, can you confirm it actually works? All my white-box attempts so far failed as those in JENKINS-44772. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.175380.1476360951000.3092.1569243121730%40Atlassian.JIRA.
[JIRA] (JENKINS-38963) User-scoped credentials cannot be looked up in pipeline
Title: Message Title Vít Zikmund commented on JENKINS-38963 Re: User-scoped credentials cannot be looked up in pipeline Hello there, Matt Sicker. If you suggest using the authorize-plugin for this purpose, can you confirm it actually works? All my white-box attempts so far failed as those in JENKINS-44772. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.175380.1476360951000.3090.1569243121708%40Atlassian.JIRA.
[JIRA] (JENKINS-38963) User-scoped credentials cannot be looked up in pipeline
Title: Message Title Matt Sicker resolved as Fixed This was implemented in JENKINS-58170, though it requires the use of credentials build parameters. Alternatively, you can use authorize-project to automate the user who is bound to the build to access their credentials. Jenkins / JENKINS-38963 User-scoped credentials cannot be looked up in pipeline Change By: Matt Sicker Status: Open Resolved Resolution: Fixed 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.175380.1476360951000.142.1566847921920%40Atlassian.JIRA.
[JIRA] (JENKINS-38963) User-scoped credentials cannot be looked up in pipeline
Title: Message Title Matt Sicker commented on JENKINS-38963 Re: User-scoped credentials cannot be looked up in pipeline This feature is improved in JENKINS-58170 and will also be supported by an upcoming release of pipeline-input-step to support user-scoped credentials prompted via an input step. 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.175380.1476360951000.21.1566847380725%40Atlassian.JIRA.
[JIRA] (JENKINS-38963) User-scoped credentials cannot be looked up in pipeline
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-38963 User-scoped credentials cannot be looked up in pipeline Change By: Jesse Glick Labels: documentation pipeline Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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.
[JIRA] (JENKINS-38963) User-scoped credentials cannot be looked up in pipeline
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-38963 User-scoped credentials cannot be looked up in pipeline Change By: Jesse Glick Labels: pipeline Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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.
[JIRA] (JENKINS-38963) User-scoped credentials cannot be looked up in pipeline
Title: Message Title Stephen Connolly commented on JENKINS-38963 Re: User-scoped credentials cannot be looked up in pipeline So to fetch user scoped credentials there are one of two conditions that must be met, either: 1. The build must be running as the user that owns the credentials (this requires the AuthorizedProject plugin be configured); or 2. The credentials must come from a credentials parameter and be selected by the user and that user must have the Credentials/USE_OWN permission (typically implied by Job/BUILD unless you request them separated out by setting a system property). If you use the default credentials in the parameter, then those will not be searched for as the idea is to prevent the user's credentials being hijacked without an explicit selection by the user triggering the build Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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.
[JIRA] (JENKINS-38963) User-scoped credentials cannot be looked up in pipeline
Title: Message Title Jesse Glick commented on JENKINS-38963 Re: User-scoped credentials cannot be looked up in pipeline Stephen Connolly knows more about user-scoped credentials. Possibly you need to use Authorized Project to associate an authentication with the build. There is no test case in this plugin that covers user-scoped credentials so as far as I am concerned it is not supported. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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.
[JIRA] (JENKINS-38963) User-scoped credentials cannot be looked up in pipeline
Title: Message Title Emmanuel Rousselle commented on JENKINS-38963 Re: User-scoped credentials cannot be looked up in pipeline I'm facing the same issue and it's not clear to me if: It's a documentation problem (the plugin is able to fetch user-scope credentials but how to do this is absent from the documentation), OR The plugin doesn't support fetching user-scope credentials at all Can someone familiar with the code clarify this? Thank you. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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.
[JIRA] (JENKINS-38963) User-scoped credentials cannot be looked up in pipeline
Title: Message Title
Martin Vehovsky commented on JENKINS-38963
Re: User-scoped credentials cannot be looked up in pipeline
Just found out, that it's possible to look-up user-scoped sredentials with '${Credentials}'
node {
withCredentials([[$class : 'UsernamePasswordMultiBinding', credentialsId: '${Credentials}',
usernameVariable: 'USERNAME', passwordVariable: 'PASSWORD']]) {
}
}
Could someone please clarify documentation for this? Thank you
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
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.
[JIRA] (JENKINS-38963) User-scoped credentials cannot be looked up in pipeline
Title: Message Title
Martin Vehovsky updated an issue
Jenkins / JENKINS-38963
User-scoped credentials cannot be looked up in pipeline
Change By:
Martin Vehovsky
It's possible to look-up User-scoped credentials in Freestyle jobs with Bindings. The same seems not to work in pipeline jobs.{code:java}node {withCredentials([[$class : 'UsernamePasswordMultiBinding', credentialsId: 'bc047678-37b8-4747-95d8-c1a8b3df51a6', usernameVariable: 'USERNAME', passwordVariable: 'PASSWORD']]) {echo "${env.USERNAME}"}}{code}{code:java}org.jenkinsci.plugins.credentialsbinding.impl.CredentialNotFoundException: bc047678-37b8-4747-95d8-c1a8b3df51a6 at org.jenkinsci.plugins.credentialsbinding.MultiBinding.getCredentials(MultiBinding.java:124) at org.jenkinsci.plugins.credentialsbinding.impl.UsernamePasswordMultiBinding.bind(UsernamePasswordMultiBinding.java:68) at org.jenkinsci.plugins.credentialsbinding.impl.BindingStep$Execution.start(BindingStep.java:92){code} Plugin versions:_credentials-binding: 1.9__credentials: 2.1.5_
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38963) User-scoped credentials cannot be looked up in pipeline
Title: Message Title Martin Vehovsky updated an issue Jenkins / JENKINS-38963 User-scoped credentials cannot be looked up in pipeline Change By: Martin Vehovsky Summary: User-scoped credentials cannot be looked up with in pipeline Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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.
[JIRA] (JENKINS-38963) User-scoped credentials cannot be looked up in pipeline
Title: Message Title
Martin Vehovsky updated an issue
Jenkins / JENKINS-38963
User-scoped credentials cannot be looked up in pipeline
Change By:
Martin Vehovsky
It's possible to look-up User-scoped credentials in Freestyle jobs with Bindings. The same seems not to works work in pipeline jobs.{code:java}node {withCredentials([[$class : 'UsernamePasswordMultiBinding', credentialsId: 'bc047678-37b8-4747-95d8-c1a8b3df51a6', usernameVariable: 'USERNAME', passwordVariable: 'PASSWORD']]) {echo "${env.USERNAME}"}}{code}{code:java}org.jenkinsci.plugins.credentialsbinding.impl.CredentialNotFoundException: bc047678-37b8-4747-95d8-c1a8b3df51a6 at org.jenkinsci.plugins.credentialsbinding.MultiBinding.getCredentials(MultiBinding.java:124) at org.jenkinsci.plugins.credentialsbinding.impl.UsernamePasswordMultiBinding.bind(UsernamePasswordMultiBinding.java:68) at org.jenkinsci.plugins.credentialsbinding.impl.BindingStep$Execution.start(BindingStep.java:92){code}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38963) User-scoped credentials cannot be looked up with pipeline
Title: Message Title
Martin Vehovsky created an issue
Jenkins / JENKINS-38963
User-scoped credentials cannot be looked up with pipeline
Issue Type:
Bug
Assignee:
Unassigned
Components:
credentials-binding-plugin
Created:
2016/Oct/13 12:15 PM
Priority:
Major
Reporter:
Martin Vehovsky
It's possible to look-up User-scoped credentials in Freestyle jobs with Bindings. The same seems not to works in pipeline jobs.
node {
withCredentials([[$class : 'UsernamePasswordMultiBinding', credentialsId: 'bc047678-37b8-4747-95d8-c1a8b3df51a6',
usernameVariable: 'USERNAME', passwordVariable: 'PASSWORD']]) {
echo "${env.USERNAME}"
}
}
org.jenkinsci.plugins.credentialsbinding.impl.CredentialNotFoundException: bc047678-37b8-4747-95d8-c1a8b3df51a6
at org.jenkinsci.plugins.credentialsbinding.MultiBinding.getCredentials(MultiBinding.java:124)
at org.jenkinsci.plugins.credentialsbinding.impl.UsernamePasswordMultiBinding.bind(UsernamePasswordMultiBinding.java:68)
at org.jenkinsci.plugins.credentialsbinding.impl.BindingStep$Execution.start(BindingStep.java:92)
