|
||||||||
|
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 cannot connect to master through JNLP after upgrading to 1.498
bron...@real-time.com (JIRA) Wed, 09 Jan 2013 08:16:59 -0800
- [JIRA] (JENKINS-16273) Slaves ... tangthe...@gmail.com (JIRA)
- [JIRA] (JENKINS-16273) Sl... tangthe...@gmail.com (JIRA)
- [JIRA] (JENKINS-16273) Sl... markusschult...@gmail.com (JIRA)
- [JIRA] (JENKINS-16273) Sl... tg...@verizon.net (JIRA)
- [JIRA] (JENKINS-16273) Sl... jgl...@cloudbees.com (JIRA)
- [JIRA] (JENKINS-16273) Sl... tg...@verizon.net (JIRA)
- [JIRA] (JENKINS-16273) Sl... ra...@java.net (JIRA)
- [JIRA] (JENKINS-16273) Sl... bron...@real-time.com (JIRA)
- [JIRA] (JENKINS-16273) Sl... bron...@real-time.com (JIRA)
- [JIRA] (JENKINS-16273) Sl... jesper.klit.jen...@intelligrated.com (JIRA)
@Jesse: This is broken for the "Logged-in users can do anything" authorization policy. The help on that suggest that this is not "security" but instead record keeping, so it really shouldn't be locked down like this. Could we allow slaves access to jnlp in this mode? Or, allow a --auth user:password option to the slave start command which doesn't seem to work right now.
Context help on "Logged-in users can do anything" from the configureSecurity page:
"This mode is useful to force users to log in before taking actions, so that you can keep record of who has done what. This setting can be also used in public-facing Jenkins, where you only allow trusted users to have user accounts."