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

[jgl...@cloudbees.com (JIRA)]

Jesse Glick commented on JENKINS-16273 Slaves forbidden to request JNLP anonymously but no clear way to pass API token The javaws command unfortunately does not seem to handle passwords or API tokens; so while curl is fine with http://user:pass@host:8080/computer/stuff/slave-agent.jnlp the same passed to javaws just gives a 403. Same for java -jar slave.jar -jnlpUrl … it seems; need to pass -jnlpCredentials to set up a headless slave, which the slave page under Connect slave to Jenkins one of these ways fails to mention. Then there is the problem that the installer fails to define -jnlpCredentials in your new jenkins-slave.xml; and JENKINS-9679 can make this not work unless you clear some obscure caches first. Seems URL.openConnection fails to parse out the username and password, or is just waiting for a BASIC auth challenge which never comes, due to Jenkins security policy?

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