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

Ldap login not working after upgrading jenkins 1.580.1 unless mark "Remember me on this computer" check box

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • ldap-plugin
    • None
    • java.version 1.7.0_06
      os.name Linux
      os.arch amd64
      os.version 2.6.32-279.22.1.el6.x86_64
      Jenkins version 1.580.1 (Long term support release)
      Jenkins Ldap plugin ldap 1.10.2

      Today we upgrade our Jenkins server to jenkins 1.580.1 ,after upgrading we are not able to login using ldap credential ,surprisingly we are able to login successful if we select the "Remember me on this computer" check box.
      We tried all the browser and cleaned the browser caches as well but getting same result.
      Please let me know if you need any other information.
      Jenkins server is running as service in linux box using "service jenkins start" command

          [JENKINS-25826] Ldap login not working after upgrading jenkins 1.580.1 unless mark "Remember me on this computer" check box

          hridyesh pant added a comment -

          Can some one please suggest a fix for this issue as it is making too much annoying to us to push user to use ""Remember me on this computer" check box" ?
          Thanks.

          hridyesh pant added a comment - Can some one please suggest a fix for this issue as it is making too much annoying to us to push user to use ""Remember me on this computer" check box" ? Thanks.

          Daniel Beck added a comment -

          The type of this issue and the presence of workaround makes this a minor issue. Critical means: crashes or loss of data.

          Daniel Beck added a comment - The type of this issue and the presence of workaround makes this a minor issue. Critical means: crashes or loss of data.

          fk_ added a comment -

          Hi, guys. I'm just wondering why this bug is considered as minor since it's show stopper for widely used in corporate environment LDAP?
          It also affect the latest LTS release and makes it impossible to upgrade from previous one.

          The only workaround is to get Jenkins source and hardcode checkbox value.

          fk_ added a comment - Hi, guys. I'm just wondering why this bug is considered as minor since it's show stopper for widely used in corporate environment LDAP? It also affect the latest LTS release and makes it impossible to upgrade from previous one. The only workaround is to get Jenkins source and hardcode checkbox value.

          Daniel Beck added a comment -

          The only workaround is to get Jenkins source and hardcode checkbox value.

          Unless you just install the Simple Theme Plugin and inject the two lines of JavaScript it takes to check the checkbox (or replace it with a hidden form field).

          Also, from the description it seems easy enough to detect, and teach your users. While certainly annoying, it does not appear to be severe.

          Daniel Beck added a comment - The only workaround is to get Jenkins source and hardcode checkbox value. Unless you just install the Simple Theme Plugin and inject the two lines of JavaScript it takes to check the checkbox (or replace it with a hidden form field). Also, from the description it seems easy enough to detect, and teach your users. While certainly annoying, it does not appear to be severe.

          Jason Kulatunga added a comment - - edited

          This was also a huge issue for us. We traced the issue to the Mailer/ext-email plugins, by verifying that a vanilla jenkins install doesn't have this issue, and then individually deleting config files until we found the culprit.
          We think it has something to do with https://issues.jenkins-ci.org/browse/JENKINS-20595
          If the hudson.tasks.Mailer.xml file exists with a hudsonUrl entry inside, and the jenkins.model.JenkinsLocationConfiguration.xml file doesn't exist, it seems that something goes horribly wrong during the login.

          Broken
          {{$ cat hudson.tasks.Mailer.xml
          <?xml version='1.0' encoding='UTF-8'?>
          <hudson.tasks.Mailer_-DescriptorImpl plugin="mailer@1.4">
          <defaultSuffix>@***.com</defaultSuffix>
          <hudsonUrl>https://***.com/</hudsonUrl>
          <adminAddress>build@***.com</adminAddress>
          <smtpHost>localhost</smtpHost>
          <useSsl>false</useSsl>
          <charset>UTF-8</charset>
          </hudson.tasks.Mailer_-DescriptorImpl>

          $ cat jenkins.model.JenkinsLocationConfiguration.xml
          cat: jenkins.model.JenkinsLocationConfiguration.xml: No such file or directory}}

          Fix 1
          Remove the hudsonUrl entry from xml file

          {{$ cat hudson.tasks.Mailer.xml
          <?xml version='1.0' encoding='UTF-8'?>
          <hudson.tasks.Mailer_-DescriptorImpl plugin="mailer@1.4">
          <defaultSuffix>@***.com</defaultSuffix>
          <adminAddress>build@***.com</adminAddress>
          <smtpHost>localhost</smtpHost>
          <useSsl>false</useSsl>
          <charset>UTF-8</charset>
          </hudson.tasks.Mailer_-DescriptorImpl>

          $ cat jenkins.model.JenkinsLocationConfiguration.xml
          cat: jenkins.model.JenkinsLocationConfiguration.xml: No such file or directory}}

          Fix 2
          Using the Jenkins manage ui, save a new Jenkins Url under Jenkins Location section. It will generate a JenkinsLocationConfiguration.xml file.

          {{$ cat hudson.tasks.Mailer.xml
          <?xml version='1.0' encoding='UTF-8'?>
          <hudson.tasks.Mailer_-DescriptorImpl plugin="mailer@1.4">
          <defaultSuffix>@***.com</defaultSuffix>
          <hudsonUrl>https://***.com/</hudsonUrl>
          <adminAddress>build@***.com</adminAddress>
          <smtpHost>localhost</smtpHost>
          <useSsl>false</useSsl>
          <charset>UTF-8</charset>
          </hudson.tasks.Mailer_-DescriptorImpl>

          $ cat jenkins.model.JenkinsLocationConfiguration.xml
          <?xml version='1.0' encoding='UTF-8'?>
          <jenkins.model.JenkinsLocationConfiguration>
          <adminAddress>Build Jenkins <build@***.com></adminAddress>
          <jenkinsUrl>http://***.com/</jenkinsUrl>
          </jenkins.model.JenkinsLocationConfiguration>}}

          Jason Kulatunga added a comment - - edited This was also a huge issue for us. We traced the issue to the Mailer/ext-email plugins, by verifying that a vanilla jenkins install doesn't have this issue, and then individually deleting config files until we found the culprit. We think it has something to do with https://issues.jenkins-ci.org/browse/JENKINS-20595 If the hudson.tasks.Mailer.xml file exists with a hudsonUrl entry inside, and the jenkins.model.JenkinsLocationConfiguration.xml file doesn't exist, it seems that something goes horribly wrong during the login. Broken {{$ cat hudson.tasks.Mailer.xml <?xml version='1.0' encoding='UTF-8'?> <hudson.tasks.Mailer_-DescriptorImpl plugin="mailer@1.4"> <defaultSuffix>@***.com</defaultSuffix> <hudsonUrl> https://***.com/ </hudsonUrl> <adminAddress>build@***.com</adminAddress> <smtpHost>localhost</smtpHost> <useSsl>false</useSsl> <charset>UTF-8</charset> </hudson.tasks.Mailer_-DescriptorImpl> $ cat jenkins.model.JenkinsLocationConfiguration.xml cat: jenkins.model.JenkinsLocationConfiguration.xml: No such file or directory}} Fix 1 Remove the hudsonUrl entry from xml file {{$ cat hudson.tasks.Mailer.xml <?xml version='1.0' encoding='UTF-8'?> <hudson.tasks.Mailer_-DescriptorImpl plugin="mailer@1.4"> <defaultSuffix>@***.com</defaultSuffix> <adminAddress>build@***.com</adminAddress> <smtpHost>localhost</smtpHost> <useSsl>false</useSsl> <charset>UTF-8</charset> </hudson.tasks.Mailer_-DescriptorImpl> $ cat jenkins.model.JenkinsLocationConfiguration.xml cat: jenkins.model.JenkinsLocationConfiguration.xml: No such file or directory}} Fix 2 Using the Jenkins manage ui, save a new Jenkins Url under Jenkins Location section. It will generate a JenkinsLocationConfiguration.xml file. {{$ cat hudson.tasks.Mailer.xml <?xml version='1.0' encoding='UTF-8'?> <hudson.tasks.Mailer_-DescriptorImpl plugin="mailer@1.4"> <defaultSuffix>@***.com</defaultSuffix> <hudsonUrl> https://***.com/ </hudsonUrl> <adminAddress>build@***.com</adminAddress> <smtpHost>localhost</smtpHost> <useSsl>false</useSsl> <charset>UTF-8</charset> </hudson.tasks.Mailer_-DescriptorImpl> $ cat jenkins.model.JenkinsLocationConfiguration.xml <?xml version='1.0' encoding='UTF-8'?> <jenkins.model.JenkinsLocationConfiguration> <adminAddress>Build Jenkins <build@***.com></adminAddress> <jenkinsUrl> http://***.com/ </jenkinsUrl> </jenkins.model.JenkinsLocationConfiguration>}}

          Oleg Nenashev added a comment -

          In order to set proper expectation, I have unassigned Kohsuke from this tickets.
          Currently there is no Default assignee in the LDAP plugin, any contributions will be appreciated.

          Oleg Nenashev added a comment - In order to set proper expectation, I have unassigned Kohsuke from this tickets. Currently there is no Default assignee in the LDAP plugin, any contributions will be appreciated.

            Unassigned Unassigned
            hridyeshpant hridyesh pant
            Votes:
            1 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: