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

Using the API Token beyond 496 causes intermittent 500 errors

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • None
    • RHEL 5.5, tomcat 6, jenkins

      After upgrading to 509 from 496, my service accounts that use the api token stopped working all the time, giving 500 errors about 1/2 the time. I tracked it down to the AD plugin complaining that the user couldn't bind correctly (which is correct as it was passing the api token).

      Switching from the AD plugin to straight LDAP fixed the issue. My best guess would be that the filters that handle the plugin and the apitoken are getting fired at different times. I stopped looking at it though once moving to LDAP solved the issue.

      thanks!

            Unassigned Unassigned
            herque herque
            Votes:
            1 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: