All our API calls are now failing. Even a simple thing like this:

      <username>:<token>@jenkins.goonies3.com/api/json

      I keep getting:

      Error 401 Unexpected authentication type: org.acegisecurity.providers.UsernamePasswordAuthenticationToken@b69dc627: Username: <username>; Password: [PROTECTED]; Authenticated: false; Details: org.acegisecurity.ui.WebAuthenticationDetails@ffff8868: RemoteIpAddress: <ip address>; SessionId: null; Not granted any authorities

      How do I get my API calls working again? This is a huge issue, it's brining most of our automated processing to a halt.

          [JENKINS-22409] API Token no longer working for API calls

          Justin Zaun created issue -

          Justin Zaun added a comment -

          I've tried version "0.15-SNAPSHOT (private-03/05/2014 10:52-soren)" of the github-oauth plugin as well from https://github.com/sorenh/github-oauth-plugin/releases and it doesn't fix the issue, APT Token still not working.

          Justin Zaun added a comment - I've tried version "0.15-SNAPSHOT (private-03/05/2014 10:52-soren)" of the github-oauth plugin as well from https://github.com/sorenh/github-oauth-plugin/releases and it doesn't fix the issue, APT Token still not working.

          Justin Zaun added a comment -

          I've downgraded back to jenkins 1.550 and the API Token starts working again. I hope I'm not stuck on v1.550 forever.

          Justin Zaun added a comment - I've downgraded back to jenkins 1.550 and the API Token starts working again. I hope I'm not stuck on v1.550 forever.

          Peter Downs added a comment -

          Experiencing the same issue on Jenkins version 1.558 and Github OAuth version 0.14 – it would be great to not have to downgrade. Any way I can help submit a fix?

          Peter Downs added a comment - Experiencing the same issue on Jenkins version 1.558 and Github OAuth version 0.14 – it would be great to not have to downgrade. Any way I can help submit a fix?

          Peter Downs added a comment - - edited

          The following version combinations all reproduce the error:

          • Jenkins v1.550 / Github OAuth v0.14
          • Jenkins v1.558 / Github OAuth v0.14
          • Jenkins v1.559 / Github OAuth v0.14

          @Justin, what combination worked for you – Jenkins v1.550 / Github OAuth v0.15-SNAPSHOT?

          Peter Downs added a comment - - edited The following version combinations all reproduce the error: • Jenkins v1.550 / Github OAuth v0.14 • Jenkins v1.558 / Github OAuth v0.14 • Jenkins v1.559 / Github OAuth v0.14 @Justin, what combination worked for you – Jenkins v1.550 / Github OAuth v0.15-SNAPSHOT?
          Fred Palmer made changes -
          Labels New: api github security

          Fred Palmer added a comment -

          Same here, same versions.

          Fred Palmer added a comment - Same here, same versions.

          Daniel Beck added a comment -

          To clarify:

          1.550 with GH OAuth 0.15-SNAPSHOT works
          1.550 with GH OAuth 0.14 does not work
          1.558 with GH OAuth 0.15-SNAPSHOT does not work

          Correct?

          This could have been caused by the fix to JENKINS-20064 in 1.556. Anyone care to confirm by testing that 1.555 works with 0.15-SNAPSHOT, and 1.556 doesn't?

          Daniel Beck added a comment - To clarify: 1.550 with GH OAuth 0.15-SNAPSHOT works 1.550 with GH OAuth 0.14 does not work 1.558 with GH OAuth 0.15-SNAPSHOT does not work Correct? This could have been caused by the fix to JENKINS-20064 in 1.556. Anyone care to confirm by testing that 1.555 works with 0.15-SNAPSHOT, and 1.556 doesn't?

          Daniel Beck added a comment -

          Possibly related to this change in 1.556.

          Daniel Beck added a comment - Possibly related to this change in 1.556.
          Daniel Beck made changes -
          Link New: This issue is related to JENKINS-20064 [ JENKINS-20064 ]

            skottler Sam Kottler
            jzaun Justin Zaun
            Votes:
            5 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: