|
||||||||
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
bron...@real-time.com (JIRA) Mon, 21 Jan 2013 14:38:58 -0800
- [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)
@Jesse - thank you for taking a closer look at this. I have resorted to running without security in hopes that a better solution will be found for the "Logged-in users can do anything" authorization policy.
How can I track SECURITY-54? Is the SECURITY project restricted from the general public? https://issues.jenkins-ci.org/secure/BrowseProjects.jspa shows the project, but it looks like it contains no issues.