|
||||||||
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 forbidden to request JNLP anonymously but -jnlpCredentials not offered
- [JIRA] (JENKINS-16273) Slaves forbidden to ... jgl...@cloudbees.com (JIRA)
- [JIRA] (JENKINS-16273) Slaves forbidde... dogf...@java.net (JIRA)
- [JIRA] (JENKINS-16273) Slaves forbidde... jgl...@cloudbees.com (JIRA)
- [JIRA] (JENKINS-16273) Slaves forbidde... bron...@real-time.com (JIRA)
- [JIRA] (JENKINS-16273) Slaves forbidde... jgl...@cloudbees.com (JIRA)
- [JIRA] (JENKINS-16273) Slaves forbidde... jgl...@cloudbees.com (JIRA)
- [JIRA] (JENKINS-16273) Slaves forbidde... scm_issue_l...@java.net (JIRA)
- [JIRA] (JENKINS-16273) Slaves forbidde... kacynski.w...@aoins.com (JIRA)
- [JIRA] (JENKINS-16273) Slaves forbidde... jgl...@cloudbees.com (JIRA)
@nerdmachine there is no need to run without security; you just need to manually specify -jnlpCredentials user:apitoken in jenkins-slave.xml.
The SECURITY project is indeed restricted. See https://wiki.jenkins-ci.org/display/JENKINS/Security+Advisories for information.