The user's credentials are only available from the user's authentication. A plugin could be written that "captures" a users authentication but that would be very bold if not written correctly
On 2 July 2014 09:04, <matthew.web...@diamond.ac.uk> wrote: > If a job requires credentials tied to a particular user scope, are those > credentials accessible if the job is timer-triggered? Triggered by an > upstream job? Triggered by an upstream job that was triggered by the user? > … by some other user? > > > > I really like the credentials work you’ve done, Stephen, but there are lot > of edge cases to consider …. > > > > Thanks > > Matthew > > > > *From:* Stephen Connolly [mailto:stephen.alan.conno...@gmail.com] > *Sent:* 01 July 2014 17:09 > *To:* jenkinsci-users@googlegroups.com > *Subject:* Re: Can Jenkins forget passwords? > > > > Well if the parameters are credentials, e.g. using the > https://wiki.jenkins-ci.org/display/JENKINS/Credentials+Binding+Plugin > and the user has tied the credentials to their own user account scope, then > the only credentials available to the build will be the global credentials > and those of the user triggering the build. > > > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
