Thanks for your reply and help. We updated the credential plugin to version 1.15 like you suggested. Afterwards, we added a credential domain for each project and added a credential with scope 'system' to each domain. Nevertheless, user of project A can use the SSH credentials of slave node from project B.
How can we see to which system a credential is tied? Thanks, martin Am 10.07.2014 13:00, schrieb Stephen Connolly: > Fixed in 1.15... Sñr Beck can get the update immediately from the update > center he uses... if you are not in that club and don't want to wait the > 8-24h for the OSS update center to pick it up you can download directly > from http://jenkins-updates.cloudbees.com/download/plugins/credentials/ > > > On 10 July 2014 11:25, Daniel Beck <[email protected]> wrote: > >> On 10.07.2014, at 12:03, Stephen Connolly <[email protected]> >> wrote: >> >>> Credentials for use against slave nodes only should be set to scope >> SYSTEM... that's what SYSTEM scope is for... gm>> >> Each credential should only be available for configuring one specific >> slave, and not the other slave. Maybe domain restrictions might work here? >> >> -- >> 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 [email protected]. >> For more options, visit https://groups.google.com/d/optout. >> >
smime.p7s
Description: S/MIME Cryptographic Signature
