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

Can't log in after plugin update

    XMLWordPrintable

Details

    • Bug
    • Status: In Progress (View Workflow)
    • Major
    • Resolution: Unresolved
    • None
    • Jenkins Ver. 2.178
      Active Directory Plugin ver. 2.15

    Description

      After update to ver. 2.15 of the Active Directory Plugin, can no longer log in to Jenkins.

      Reverting to ver 2.14 allows me to log in once more.

      With Anonymous admin allowed, I enabled logging and the log shows that I have logged in successfully:

      but I always get the message "Invalid username or password":

       

      Attachments

        Issue Links

          Activity

            sergiolabres Sergio Labres added a comment -

            No progress in this issue ?

            sergiolabres Sergio Labres added a comment - No progress in this issue ?
            peejay Paul Adams added a comment -

            martinboer, we are talking here about the Active Directory Plugin, not the LDAP plugin. All my plugins are always up to date.

            peejay Paul Adams added a comment - martinboer , we are talking here about the Active Directory Plugin, not the LDAP plugin. All my plugins are always up to date.
            martinboer Martin Boer added a comment -

            When you run into this error, I'd recommend to update your plugins asap afterwards, that seems to be the underlying issue.

            My 2 cents.

            martinboer Martin Boer added a comment - When you run into this error, I'd recommend to update your plugins asap afterwards, that seems to be the underlying issue. My 2 cents.
            martinboer Martin Boer added a comment -

            We have several Jenkins instances, some of them working after the upgrade, some not.

            We copied the ldap.hpi file in /var/lib/jenkins/plugins/ with filesize 129449 to systems with ldap.jpi with filesize 101895, and removed the latter.

            Restart jenkins; it renames the ldap.hpi to ldap.jpi and still fails with ldap

            ln -s ldap.jpi ldap.hpi

            Restart jenkins and success

             

            martinboer Martin Boer added a comment - We have several Jenkins instances, some of them working after the upgrade, some not. We copied the ldap.hpi file in /var/lib/jenkins/plugins/ with filesize 129449 to systems with ldap.jpi with filesize 101895, and removed the latter. Restart jenkins; it renames the ldap.hpi to ldap.jpi and still fails with ldap ln -s ldap.jpi ldap.hpi Restart jenkins and success  
            peejay Paul Adams added a comment -

            wfollonier, I switched on the logging and all I received in the log was "Login Successful" as shown in the screenshot, no errors are displayed.

            FYI, the problem shows itself on Windows 2012 R2 server and Windows 10 local PC.

            peejay Paul Adams added a comment - wfollonier , I switched on the logging and all I received in the log was "Login Successful" as shown in the screenshot, no errors are displayed. FYI, the problem shows itself on Windows 2012 R2 server and Windows 10 local PC.

            People

              fbelzunc Félix Belzunce Arcos
              peejay Paul Adams
              Votes:
              4 Vote for this issue
              Watchers:
              11 Start watching this issue

              Dates

                Created:
                Updated: