If your command line is something like "java -jar slave.jar -jnlpUrl http://host/path/to/jnlp";, then the right thing to do is to use the -jnlpCredentials option. But as SBreitBach discovered, due to a missing dependency problem it turns out this doesn't work (Ugh!). This is being fixed now.
In the mean time, what I recommend is to manually download the JNLP file from your browser, then have -jnlpUrl point to the local copy via file:///path/to/local.jnlp I'm not really sure what the -auth option does, even though I added it :-( 2013/1/11 <matthew.web...@diamond.ac.uk> > 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:* jenkinsci-users@googlegroups.com [mailto: > jenkinsci-users@googlegroups.com] *On Behalf Of * > stuart.gr...@doccentrics.com > *Sent:* 11 January 2013 10:39 > *To:* jenkinsci-users@googlegroups.com > *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 **** > -- Kohsuke Kawaguchi
