Jenkins Personal Credentials

[Jörg Steffen]

Hi all,

we are using Jenkins 1.624 together with the Credentials plugin 1.22 and have set the security realm to
Jenkins’ own user database. According to the documentation of the Credentials plugin, a user can add personal credentials via "Users"/ your username / "Configure". This works fine, but the credentials entered are not available when creating a new job. In the "Source Code Management" section, neither for Subversion nor Git the personal credentials can be selected. Only credentials that have been set "globally" are available.

Is there any way to make the personal credentials available?

Best regards,
Jörg

[Cyrille Le Clerc]

Hi all,

For the record, we have recently opened

• JENKINS-44773 User Scoped credentials are not used by the "git" pipeline step
• JENKINS-44774 User Scoped credentials don't appear in credentials drop down lists

Cyrille

[Stephen Connolly]

You want the https://plugins.jenkins.io/authorize-project plugin... then you can configure the job to run as the user... and because the default authentication of the job will then be that of the user they get the credentials from the per-user store:

There is a lot of misunderstanding of how credentials are intended to be used by plugins and by users. I am currently attempting to document the design in https://github.com/jenkinsci/credentials-plugin/tree/master/docs 

--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/f58a94f3-a69c-476a-aa1c-ff9a0b7e845c%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Stephen Connolly]

On 19 July 2017 at 04:41, Stephen Connolly <stephen.al...@gmail.com> wrote:

You want the https://plugins.jenkins.io/authorize-project plugin... then you can configure the job to run as the user... and because the default authentication of the job will then be that of the user they get the credentials from the per-user store:

There is a lot of misunderstanding of how credentials are intended to be used by plugins and by users. I am currently attempting to document the design in https://github.com/jenkinsci/credentials-plugin/tree/master/docs 

Due to the misunderstanding of how to use credentials, a lot of plugin authors have not actually integrated the credentials selection stuff the intended way and you will see this as the credentials available not being aligned with the actual credentials available... so if we look at the subversion plugin, for example, it is not respecting Tasks.getAuthenticationOf(), so you see the wrong credentials in the drop-down:

Now I'm not blaming the plugin authors, the reality is that I have been begging my paymasters to give me a window of time to document the user, consumer and implementation guides for 5 years... I got that window on Friday... ;-)

Here's the consumer plugin guide on how to populate the drop-down list: https://github.com/jenkinsci/credentials-plugin/blob/master/docs/consumer.adoc#listing-available-credentials-matching-some-specific-set-of-criteria