Thanks Matthew, I'm a complete newbie with jenkins, I only started at this workplace a week ago and this update landed! Going through my log I certainly had the 403 errors and ticked various anonymous access rights to get it to connect again. I've just got it working after I noticed that it had moved onto a 401 error which prompted me to get the jnlp credentials(which look much like an api key) for our jenkins linux slave user account, I reapplied it as the password in the jenkins master and its now connecting, even with all the anonymous privileges revoked.
Cheers. Stuart Green On Friday, 11 January 2013 10:55:18 UTC, matthew...@diamond.ac.uk wrote: > > From a message I sent to the list a few days ago, which worked for at > least some people: > > > > >>> > > I was in a slightly different situation (linux, slaves launched manually), > but had the 403 as well. Fixed by going to Manage Jenkins -> Configure > Global Security, and under Project-based Matrix Authorization Strategy I > had to enable “connect” in the “slave” section, for user “Anonymous”. > > <<< > > > > I’m not sure if that address your problem, of what the security > implications are, but anyhow … > > > > Matthew Webber > > > > *From:* jenkins...@googlegroups.com <javascript:> [mailto: > jenkins...@googlegroups.com <javascript:>] *On Behalf Of * > stuart...@doccentrics.com <javascript:> > *Sent:* 11 January 2013 10:39 > *To:* jenkins...@googlegroups.com <javascript:> > *Subject:* Re: JNLP slave no longer works > > > > > > Thanks for the info, but how is this change applied to a linux slave? > > > On Tuesday, 8 January 2013 02:50:39 UTC, Kohsuke Kawaguchi wrote: > > This is unfortunately a necessary measure. > > > > See the "Fix" section in > https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2013-01-04 > > > > > -- > Kohsuke Kawaguchi >
