Yes, you just need to re-download the JNLP file from the master and overwrite the local copy at the slave.
2013/1/7 Jon Schewe <jpsch...@mtu.net> > OK, so if I just keep the jnlp local now instead of always requesting it > on startup, thing will continue to work, correct? > > > On Monday, January 7, 2013, 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 >> >> >> 2013/1/7 Jon Schewe <jpsch...@mtu.net> >> >>> I just upgraded to 1.480.2 from 1.471 and my JNLP slaves can no longer >>> connect. I get an error: >>> >>> JNLPException[category: Download Error : Exception: java.io.IOException: >>> Server returned HTTP response code: 403 for URL: >>> https://server:8010/computer/slave-jnlp/slave-agent.jnlp : LaunchDesc: >>> null ] >>> at com.sun.javaws.Main.launchApp(Unknown Source) >>> at com.sun.javaws.Main.continueInSecureThread(Unknown Source) >>> at com.sun.javaws.Main$1.run(Unknown Source) >>> at java.lang.Thread.run(Unknown Source) >>> >>> I have security turned on, although anonymous has overall read. What >>> other permissions do I need to change? What are my options? >>> >>> -- >>> http://mtu.net/~jpschewe >>> >>> >> >> >> -- >> Kohsuke Kawaguchi >> > > > -- > On my mobile device - please excuse typos > -- Kohsuke Kawaguchi
