Credentials for use against slave nodes only should be set to scope SYSTEM... that's what SYSTEM scope is for...
On 10 July 2014 09:21, martin flehmig <[email protected]> wrote: > Dear Jenkins community! > > We have the following problem: > > * We have two (disjunct) projects A and B each with several jobs that > are organized in folders (using the folder plugin) according to the > related project. > * We have configured an Unix slave node for each project (called NA,NB). > Basically the slave nodes are the very same machines, but the ssh > credentials differ because of the different projects. > * Project A and slave node NA can only be configured by user UA. > * Project B and slave node NB can only be configured by user UB (!=UA). > > Currently, user UA can use the credentials of slave node NB when > configuring slave node NA and vice versa: > a) configuring slave node NA: > credentials CNA, CNB can be seen and used. > b) configuring slave node NB: > credentials CNA, CNB can be seen and used. > > How can we prevent this? > > Thanks, > martin > > > -- > Martin Flehmig > Technische Universität Dresden > Zentrum für Informationsdienste und Hochleistungsrechnen (ZIH) > Zellescher Weg 12, 01062 Dresden > WIL A103 > Tel. +49 351 463 42303 > Fax. +49 351 463 37773 > Email: [email protected] > > -- 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.
