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

Latest LTS causes swarm clients fail to authenticate when using github-oauth

XMLWordPrintable

      Upgrading to the latest LTS version (1.532.2) caused all our swarm clients to fail to connect. Reverting to the previous version (1.532.1) resolved the issue.

      They all failed with an authentication failure. We're using the github-oauth plugin. The slave user below has been manually created on the server, and given an API token, which is being used as the password. I've managed to reproduce this using curl as follows.

      Against 1.532.2:

      $ curl --user slave https://jenkins.example.com/plugin/swarm/slaveInfo
Enter host password for user 'slave':
<html><head><title>Error 401</title></head>
<body bgcolor="#ffffff"><h1>Status Code: 401</h1>Exception: Unexpected authentication type: org.acegisecurity.providers.UsernamePasswordAuthenticationToken@661c7182: Username: slave; Password: [PROTECTED]; Authenticated: false; Details: org.acegisecurity.ui.WebAuthenticationDetails@0: RemoteIpAddress: 192.168.0.3; SessionId: null; Not granted any authorities<br>
Stacktrace: <pre>(none)
</pre><br>
<hr size="1" width="90%"><i>Generated by Winstone Servlet Engine v0.9.10 at Thu Feb 20 10:48:18 UTC 2014</i></body></html>

      Same command against 1.532.1:

      $ curl --user slave https://jenkins.example.com/plugin/swarm/slaveInfo
Enter host password for user 'slave':
<slaveInfo><swarmSecret>12345678-1234-1234-1234-123456789abc</swarmSecret></slaveInfo>

      This may be a duplicate of JENKINS-17539, but the symptoms are different.

          [JENKINS-21895] Latest LTS causes swarm clients fail to authenticate when using github-oauth

            sag47 Sam Gleske
            apdt Alex Tomlins
            Votes:
            2 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: