Le mardi 6 juin 2017 21:56:33 UTC+2, Jesse Glick a écrit : > > On Tue, Jun 6, 2017 at 1:27 PM, Arvid Huss <[email protected] > <javascript:>> wrote: > > I have already been in contact with the plugin developer and he refered > me > > to jenkins-dev mailing list. > > Well they will need to do some more evaluation on their end. >
Hi guys, I'm sorry if I missed something obvious, this is not my intention to pass the buck, but the documentation <https://wiki.jenkins-ci.org/display/JENKINS/Action+and+its+family+of+subtypes> says: > There's a variant of this called UnprotectedRootAction > <http://javadoc.jenkins-ci.org/byShortName/UnprotectedRootAction> that is > made accessible even to anonymous users without the read access to Jenkins. Also we are doing a very similar implementation than what the Jenkins GitHub plugin does. Finally I made a simple test (run Jenkins 2.64, enable security, disable anonymous read) and everything looks fine. So if on Jenkins side you confirm there is no regression, my last guess for this 403 error would be that there is an issue on your side Arvid. Maybe you could try to temporarily enable anonymous read to see if that bring back access to the <jenkins>/sonarqube-webhook/ URL. Also you can try to access your Jenkins server without using the proxy (just to eliminate it from the equation). ++ Julien -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" 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-dev/f4aec9f4-4f08-41b5-8bfe-9d124b6d944a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
