Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-3734

Can't launch Windows slave via JNLP when Hudson authentication enabled

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Critical Critical
    • core
    • None
    • Platform: All, OS: All

      We have configured Hudson security to disallow anonymous access and set read
      access for authenticated users. I noticed though that the Windows slave we have
      registered can no longer launch. In the slave log we see:

      Failing to obtain http://HUDSON.xxxx.com/computer/XXXXXXXX/slave-agent.jnlp
      java.io.IOException: Failed to load
      http://HUDSON.xxxx.com/computer/XXXXXXXX/slave-agent.jnlp: 403 Forbidden
      at hudson.remoting.Launcher.parseJnlpArguments(Launcher.java:194)
      at hudson.remoting.Launcher.run(Launcher.java:169)
      at hudson.remoting.Launcher.main(Launcher.java:154)
      Waiting 10 seconds before retry

      I noticed that I can still successfully launch my *nix slave that execute a wget
      -O slave.jar http://HUDSON.xxxx.com/jnlpJars/slave.jar. This path must not be
      protected in the Hudson config while the /computer path is.

          [JENKINS-3734] Can't launch Windows slave via JNLP when Hudson authentication enabled

          Peter Hayes created issue -
          larsko made changes -
          Link New: This issue duplicates JENKINS-2774 [ JENKINS-2774 ]
          Harry G. made changes -
          Link New: This issue duplicates JENKINS-4071 [ JENKINS-4071 ]
          Harry G. made changes -
          Link New: This issue is related to JENKINS-9679 [ JENKINS-9679 ]
          Jesse Glick made changes -
          Resolution New: Duplicate [ 3 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 133807 ] New: JNJira + In-Review [ 186686 ]

            Unassigned Unassigned
            petehayes Peter Hayes
            Votes:
            9 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: