LDAPS connections no longer work as of version 2.25.1

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

      Since updating to version 2.25.1 of the active-directory plugin, we can no longer establish a connection to our LDAPS server. This is probably related to the removal of the forceLdaps argument.

      Attempting to connect to and LDAPS server produces the following error:

      LDAP connection has been closed javax.naming.NamingException: LDAP connection has been closed at java.naming/com.sun.jndi.ldap.LdapRequest.getReplyBer(LdapRequest.java:133) at java.naming/com.sun.jndi.ldap.Connection.readReply(Connection.java:443) at java.naming/com.sun.jndi.ldap.LdapClient.ldapBind(LdapClient.java:365) at java.naming/com.sun.jndi.ldap.LdapClient.authenticate(LdapClient.java:214) at java.naming/com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2895) at java.naming/com.sun.jndi.ldap.LdapCtx.ensureOpen(LdapCtx.java:2797) at java.naming/com.sun.jndi.ldap.LdapCtx.ensureOpen(LdapCtx.java:2770) at java.naming/com.sun.jndi.ldap.LdapCtx.reconnect(LdapCtx.java:2699) at hudson.plugins.active_directory.ActiveDirectorySecurityRealm$DescriptorImpl.bind(ActiveDirectorySecurityRealm.java:723) at hudson.plugins.active_directory.ActiveDirectorySecurityRealm$DescriptorImpl.bind(ActiveDirectorySecurityRealm.java:601) at hudson.plugins.active_directory.ActiveDirectorySecurityRealm$DescriptorImpl.bind(ActiveDirectorySecurityRealm.java:566) at hudson.plugins.active_directory.ActiveDirectoryDomain$DescriptorImpl.doValidateTest(ActiveDirectoryDomain.java:337) at ...

            Assignee:
            Nik Reiman
            Reporter:
            Nik Reiman
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: