[JIRA] (JENKINS-14524) Slave agent authorization 401
Craig Ringer commented on JENKINS-14524 Slave agent authorization 401 As a workaround, you can save slave-agent.jnlp from the worker's page on the Jenkins server to c:\jenkins (or wherever your jenkins root on the slave is), then modify jenkins-slave.xml to point to file:///C:/jenkins/slave-agent.jnlp instead of the Jenkins URL. This will prevent the slave from getting automatic updates from Jenkins, so you'll have to replace the jnlp file and restart the slave agent yourself if you upgrade Jenkins. Alternately, you can enable anonymous READ for all users. 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-14524) Slave agent authorization 401
Craig Ringer commented on JENKINS-14524 Slave agent authorization 401 Related to JENKINS-11149 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-14524) Slave agent authorization 401
Craig Ringer updated JENKINS-14524 Slave agent authorization 401 Change By: Craig Ringer (20/Dec/12 6:13 AM) Priority: Critical Major 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-14524) Slave agent authorization 401
Craig Ringer
updated JENKINS-14524
Slave agent authorization 401
Amended report to tag github-oauth, tweak formatting.
Change By:
Craig Ringer
(20/Dec/12 5:49 AM)
Description:
I can connect my slave agent using the downloaded jnlp file, but Windows service is not working because of authorization.My configuration looks like this:
{code}
-Xrs -jar "%BASE%\slave.jar" -auth xxx:xxx -jnlpUrl http://xxx.dyndns.org/computer/windows/slave-agent.jnlp -cp "%BASE%\lib\commons-codec-1.5.jar" -jnlpCredentials xxx:xxx
{code}
And in logs I see:
{code}
Failing to obtain http://homersoft-ci.dyndns.org/computer/windows/slave-agent.jnlpjava.io.IOException: Failed to load http://xxx.dyndns.org/computer/windows/slave-agent.jnlp: 403 Forbidden at hudson.remoting.Launcher.parseJnlpArguments(Launcher.java:230) at hudson.remoting.Launcher.run(Launcher.java:192) at hudson.remoting.Launcher.main(Launcher.java:168)
{code}I'm using the GitHub OAuth plugin.
Component/s:
github-oauth
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-14524) Slave agent authorization 401
Craig Ringer commented on JENKINS-14524 Slave agent authorization 401 Yeah, the GitHub plugin needs to allow an exception for the JNLP file, or preferably generate a unique per-worker username/password that it displays in the JNLP launch commands and uses automatically in the service. Not trivial to do, though. 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-14524) Slave agent authorization 401
Łukasz Nowak created JENKINS-14524 Slave agent authorization 401 Issue Type: Bug Affects Versions: current Assignee: Kohsuke Kawaguchi Components: slave-setup Created: 20/Jul/12 11:14 PM Description: I can connect my slave agent using the downloaded jnlp file, but Windows service is not working because of authorization. My configuration looks like this: -Xrs -jar "%BASE%\slave.jar" -auth xxx:xxx -jnlpUrl http://xxx.dyndns.org/computer/windows/slave-agent.jnlp -cp "%BASE%\lib\commons-codec-1.5.jar" -jnlpCredentials xxx:xxx And in logs I see: Failing to obtain http://homersoft-ci.dyndns.org/computer/windows/slave-agent.jnlp java.io.IOException: Failed to load http://xxx.dyndns.org/computer/windows/slave-agent.jnlp: 403 Forbidden at hudson.remoting.Launcher.parseJnlpArguments(Launcher.java:230) at hudson.remoting.Launcher.run(Launcher.java:192) at hudson.remoting.Launcher.main(Launcher.java:168) Environment: Debian as Master, Windows 2008 as Slave Project: Jenkins Priority: Critical Reporter: Łukasz Nowak 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
