Is there a way to restrict which run as credentials can be used? I don’t want everyone who can run scripts allowed to pick any run as credential they want. Would like to be able to restrict if possible.
Seperate secrets is one of the reasons for why we use multiple IIS sites under seperate service accounts.
it doesnt solve the run-as issue, as runas cant work under IIS like that - but it does work for secrets in general.
I have multiple users, each with their own credentials for external secured servers needed to run their builds. I am using the credentials plugin to manage the stored credentials. Currently, when a user configures a project, they can use anyones credentials for doing external jobs. I need to make it so that each user only sees the credentials they own when they configure jobs on the jenkins server. How would I do this?