I was never able to find one. I suspect that what will be required is some sort of 'token' that can be embedded into the webhook URL and will provide rudimentary authentication to Jenkins, but I have no idea if there is any mechanism today to provide that.
----- Original Message ----- From: jenkinsci-users@googlegroups.com To: jenkinsci-users@googlegroups.com At: Apr 9 2014 15:44:13 I agree that it's not a great solution but it'll get me by while I search for a more favorable one. Is there another way to utilize the webhook feature without enabling any anon privileges? ----- Original Message ----- From: "Kevin Fleming (BLOOMBERG/ 731 LEXIN)" <kpflem...@bloomberg.net> To: jenkinsci-users@googlegroups.com Sent: Wednesday, April 9, 2014 2:07:17 PM Subject: Re: Enabling Jenkins Security Blocks Github Webook <404 Error> Keep in mind that this will allow anyone to kick off builds of your jobs if they can reach your Jenkins web interface. This may not be a concern for you, but something to think about. ----- Original Message ----- From: jenkinsci-users@googlegroups.com To: jenkinsci-users@googlegroups.com At: Apr 9 2014 14:25:54 Ah, no. Apologies, forgot to remove that. Initially I had it enabled as disabling it seemed to break the webhook feature. Today with Jobs:configure off, it seems to work fine. To clarify - Jobs: Read, Build | Overall: read ----- Original Message ----- From: "Kevin Fleming (BLOOMBERG/ 731 LEXIN)" <kpflem...@bloomberg.net> To: jenkinsci-users@googlegroups.com Sent: Tuesday, April 8, 2014 4:18:12 PM Subject: Re: Enabling Jenkins Security Blocks Github Webook <404 Error> You are allowing 'anonymous' to configure your jobs? That sounds quite bad. ----- Original Message ----- From: jenkinsci-users@googlegroups.com To: jenkinsci-users@googlegroups.com At: Apr 8 2014 17:05:42 >> My security matrix grants Overall and Job Read to Anonymous. That did the trick. After some fidgeting with anon permissions, the following allowed git to push the build. Overall: +read and Jobs: +configure +read +build -- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
