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
- is related to
-
-
- Open
-
Activity
Paul Adams
created issue -
Björn Olsson
added a comment - Me too, I upgrade to 2.15, and i get the "invalid username or password" error message. downgrade to 2.14 and it works again.
Björn Olsson
added a comment - Me too, I upgrade to 2.15, and i get the "invalid username or password" error message. downgrade to 2.14 and it works again. 
Borja Domínguez
added a comment - I suffered the same yesterday and I was able to solve it.
NOTE: First of all make a backup of Jenkins in case you lose any security settings.
The first thing I did was to uncheck "Enable security" to at least be able to access it.
The second thing I did to make it work for me is to configure everything by hand, that is, it is not enough to check "Active Directory" in Security Realm. You have to check "Specify custom Active Directory domain name" and add a domain manually with all its configuration.
Borja Domínguez
added a comment - I suffered the same yesterday and I was able to solve it.
NOTE : First of all make a backup of Jenkins in case you lose any security settings.
The first thing I did was to uncheck "Enable security" to at least be able to access it.
The second thing I did to make it work for me is to configure everything by hand, that is, it is not enough to check "Active Directory" in Security Realm. You have to check "Specify custom Active Directory domain name" and add a domain manually with all its configuration. 
Neil Sleightholm
added a comment - Same problem for me - is there any information I can add to help resolve the issue?
Duplicate here JENKINS-57635
Neil Sleightholm
added a comment - Same problem for me - is there any information I can add to help resolve the issue?
Duplicate here JENKINS-57635 | Field | Original Value | New Value |
|---|---|---|
| Status | Open [ 1 ] | In Progress [ 3 ] |
Sorry, it is strange. the plugin has integration tests to avoid this.
I will test this asap and try to fix the problem.
Neil Sleightholm
added a comment - For me yes, Windows Server 2012. peejay, nsleigh, joshschreuder, bdominguez, sergiolabres, ursus_b, sergiolabres, 5imon, could you provide a bit of log in addition to the existing screenshot?
That could be especially useful to detect where the root cause is.
Thank you in advance!
Neil Sleightholm
added a comment - Can you let me know the log file name? nsleigh You can follow the information on this page: Logging doc, to retrieve the log file, I hope this will help you!
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.
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. 
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
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
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.
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. 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.
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. | Link | This issue is related to JENKINS-57569 [ JENKINS-57569 ] |
Same issue here, manually rolled back to 2.14 and was able to login.