"Test Settings" of LDAP User Mapping always fails

Description

Steps to reproduce:
1. Configure Openfire against an LDAP server
2, Access Server -> Server Settings -> Profile Settings (http://localhost:9090/profile-settings.jsp)
3. Click "Edit", then "Save and Continue" to move to User Mapping settings
4. Click "Test Settings"

Expected results:

  • The test indicates that the settings are working

Actual results:

  • The test indicates:

    Status: Error

    No users were found using the specified configuration. Try changing the base DN, user filter or username field.

Checking the error log reveals:

2019.11.23 17:04:41 ERROR [Jetty-QTP-AdminConsole-35]: org.jivesoftware.util.Log - Error occurred while trying to get users data from LDAP
{{ javax.naming.NamingException: [LDAP: error code 1 - 000004DC: LdapErr: DSID-0C0907C2, comment: In order to perform this operation a successful bind must be completed on the connection., data 0, v2580 ]}}
{{ at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3194) ~[?:1.8.0_212]}}
{{ at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:3100) ~[?:1.8.0_212]}}
{{ at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2891) ~[?:1.8.0_212]}}
{{ at com.sun.jndi.ldap.LdapCtx.searchAux(LdapCtx.java:1846) ~[?:1.8.0_212]}}
{{ at com.sun.jndi.ldap.LdapCtx.c_search(LdapCtx.java:1769) ~[?:1.8.0_212]}}
{{ at com.sun.jndi.toolkit.ctx.ComponentDirContext.p_search(ComponentDirContext.java:392) ~[?:1.8.0_212]}}
{{ at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.search(PartialCompositeDirContext.java:358) ~[?:1.8.0_212]}}
{{ at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.search(PartialCompositeDirContext.java:341) ~[?:1.8.0_212]}}
{{ at javax.naming.directory.InitialDirContext.search(InitialDirContext.java:267) ~[?:1.8.0_212]}}
{{ at org.jivesoftware.admin.LdapUserTester.getSample(LdapUserTester.java:118) ~[xmppserver-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT]}}
{{ at org.jivesoftware.openfire.admin.setup.setup_002dldap_002duser_005ftest_jsp._jspService(setup_002dldap_002duser_005ftest_jsp.java:173) [xmppserver-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT]}}
{{ at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) [apache-jsp-8.5.40.jar:8.5.40]}}
{{ at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) [javax.servlet-api-3.1.0.jar:3.1.0]}}
{{ at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:873) [jetty-servlet-9.4.18.v20190429.jar:9.4.18.v20190429]}}
{{ ...}}

Environment

None

is related to

Activity

Show:

Guus der Kinderen November 23, 2019 at 7:18 PM
Edited

In addition to fixing the problem that's causing the test to fail: how is it that a failed test gets reported to be A-OK. That smells...

Update: nevermind, I misread.

Greg Thomas November 23, 2019 at 6:11 PM

Introduced by

Greg Thomas November 23, 2019 at 6:07 PM

Yup!

wroot November 23, 2019 at 5:45 PM

Maybe it should be classified as a bug?

Fixed

Details

Assignee

Reporter

Components

Fix versions

Affects versions

Priority

Created November 23, 2019 at 5:13 PM
Updated January 10, 2020 at 4:40 PM
Resolved November 24, 2019 at 12:15 PM