[JIRA] (JENKINS-16273) Slaves forbidden to request JNLP anonymously but no clear way to pass API token

[oldel...@java.net (JIRA)]

Richard Mortimer commented on JENKINS-16273 Slaves forbidden to request JNLP anonymously but no clear way to pass API token I managed to fix this fairly simply on my windows slaves (tested on XP, Vista & Win 7). 1 - autheticate as a Jenkins admin in a browser of your choice and download the slave-agent.jnlp file for the slave. The download URL will be something like http://<jenkinsurl>/computer/<slavename>/slave-agent.jnlp and can be found in the jenkins-slave.xml file on the slave. 2 - transfer slave-agent.jnlp to the slave and store in the same folder as slave.jar and jenkins-slave.xml files 3 - edit jenkins-slave.xml and change the URL of slave-agent.jnlp to be file:///%BASE%/slave-agent.jnlp That means that the arguments line in jenkins-slave.xml will likely read <arguments>-Xrs -jar "%BASE%\slave.jar" -jnlpUrl file:///%BASE%/slave-agent.jnlp</arguments> Now just start the slave service as normal and all should work. Disclaimer: I haven't studied the security implications of storing slave-agent.jnlp at that location in the slave. I suspect it is fine but it would be good if someone could comment on whether there is a better location.

This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira