- 
    Bug 
- 
    Resolution: Duplicate
- 
    Critical 
- 
    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.
- duplicates
- 
                    JENKINS-2774 Provide authentication between master/slave machines -         
- Closed
 
-         
- 
                    JENKINS-4071 jnlp slaves doesn't support HTTP Auth -         
- Closed
 
-         
- is related to
- 
                    JENKINS-9679 NoClassDefFoundError on Base64 when launching an headless slave with -jnlpCredential option -         
- Closed
 
-