> On 7. Sep 2017, at 18:53, Daniel Lo Nigro <[email protected]> wrote: > > I guess this is due to SECURITY-201 > (https://jenkins.io/security/advisory/2017-07-10/) but now I'm not quite sure > how to accomplish what I want. How can I allow the projects to be triggered > as downstream builds of a remotely-triggered build, without allowing > anonymous users to trigger them directly?
It looks like you have Authorize Plugin (or another plugin providing build authorization) installed, but are not using it -- change that. -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/C4372D56-ECE6-4512-BACD-AC04F9F7DC2B%40beckweb.net. For more options, visit https://groups.google.com/d/optout.
