|
||||||||||||||
|
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 |
||||||||||||||
- [JIRA] (JENKINS-16273) Slaves ... [email protected] (JIRA)
- [JIRA] (JENKINS-16273) Sl... [email protected] (JIRA)
- [JIRA] (JENKINS-16273) Sl... [email protected] (JIRA)
- [JIRA] (JENKINS-16273) Sl... [email protected] (JIRA)
- [JIRA] (JENKINS-16273) Sl... [email protected] (JIRA)
- [JIRA] (JENKINS-16273) Sl... [email protected] (JIRA)
- [JIRA] (JENKINS-16273) Sl... [email protected] (JIRA)
- [JIRA] (JENKINS-16273) Sl... [email protected] (JIRA)
- [JIRA] (JENKINS-16273) Sl... [email protected] (JIRA)
- [JIRA] (JENKINS-16273) Sl... [email protected] (JIRA)

This is intentional—part of the security fix. In order to retrieve slave-agent.jnlp now, you need to provide authentication demonstrating that you are permitted to connect to the slave. This is generally done using an API token. Alternately, download the JNLP from your browser (while logged in as an admin) and save that, rather than attempting to connect to slave-agent.jnlp on the fly.
@trevora: granting the Anonymous user the "Connect" privilege effectively bypasses (part of) the security fix. Do not do this unless you are on a trusted, closed network (in which case why are you running with security at all?).