jenkinsci / jenkinsci/active-directory-plugin
[JENKINS-64111] AD Authentication Does not Work for Jenkins Login
- Dominant language
- Java
- Stars
- 53
- Forks
- 115
- PR merge metrics
- No merged PRs in 30d
Description
Hi, we have been using Jenkins authentication with AD plugin and it was working fine since last Friday, on this weekend we had restarted our Jenkins Server and since then we are not able to Login to Jenkins and gets below error.
[LDAP: error code 8 - 00002028: LdapErr: DSID-0C09026E, comment: The server requires binds to turn on integrity checking if SSL\TLS are not already active on the connection, data 0, v2580]
javax.naming.AuthenticationNotSupportedException: [LDAP: error code 8 - 00002028: LdapErr: DSID-0C09026E, comment: The server requires binds to turn on integrity checking if SSL\TLS are not already active on the connection, data 0, v2580]
at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3252)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:3207)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2993)
at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2907)
at com.sun.jndi.ldap.LdapCtx.ensureOpen(LdapCtx.java:2799)
at com.sun.jndi.ldap.LdapCtx.ensureOpen(LdapCtx.java:2772)
at com.sun.jndi.ldap.LdapCtx.reconnect(LdapCtx.java:2697)
at hudson.plugins.active_directory.ActiveDirectorySecurityRealm$DescriptorImpl.bind(ActiveDirectorySecurityRealm.java:666)
at hudson.plugins.active_directory.ActiveDirectorySecurityRealm$DescriptorImpl.bind(ActiveDirectorySecurityRealm.java:544)
at hudson.plugins.active_directory.ActiveDirectoryDomain$DescriptorImpl.doValidateTest(ActiveDirectoryDomain.java:336)
All the AD certificates are store in the keystore and it was working fine but after restart on weekend we are not able to login, AD plugin configuration remains same.
---
Originally reported by bhardwajme, imported from: AD Authentication Does not Work for Jenkins Login
fbelzunc
Raw content of original issue
Hi, we have been using Jenkins authentication with AD plugin and it was working fine since last Friday, on this weekend we had restarted our Jenkins Server and since then we are not able to Login to Jenkins and gets below error.
[LDAP: error code 8 - 00002028: LdapErr: DSID-0C09026E, comment: The server requires binds to turn on integrity checking if SSL\TLS are not already active on the connection, data 0, v2580]
javax.naming.AuthenticationNotSupportedException: [LDAP: error code 8 - 00002028: LdapErr: DSID-0C09026E, comment: The server requires binds to turn on integrity checking if SSL\TLS are not already active on the connection, data 0, v2580]
at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3252)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:3207)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2993)
at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2907)
at com.sun.jndi.ldap.LdapCtx.ensureOpen(LdapCtx.java:2799)
at com.sun.jndi.ldap.LdapCtx.ensureOpen(LdapCtx.java:2772)
at com.sun.jndi.ldap.LdapCtx.reconnect(LdapCtx.java:2697)
at hudson.plugins.active_directory.ActiveDirectorySecurityRealm$DescriptorImpl.bind(ActiveDirectorySecurityRealm.java:666)
at hudson.plugins.active_directory.ActiveDirectorySecurityRealm$DescriptorImpl.bind(ActiveDirectorySecurityRealm.java:544)
at hudson.plugins.active_directory.ActiveDirectoryDomain$DescriptorImpl.doValidateTest(ActiveDirectoryDomain.java:336)
All the AD certificates are store in the keystore and it was working fine but after restart on weekend we are not able to login, AD plugin configuration remains same.
environment
```
OS - Distributor ID: Ubuntu
Description: Ubuntu 18.04.4 LTS
Release: 18.04
Codename: bionic
Jenkins - 2.264
AD Plugin - 2.19
Java - Open JDK
```
Contributor guide
Research direction
Start with the stack trace locations in ActiveDirectorySecurityRealm.java, especially DescriptorImpl.bind, and ActiveDirectoryDomain.java at DescriptorImpl.doValidateTest. Reproduce the LDAP bind failure using the reported Jenkins 2.264, AD Plugin 2.19, Ubuntu 18.04, and Java environment. Done means AD authentication and Jenkins login work again with the existing configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- authentication, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100