ejabberd - Comments for "LDAP authentication error"

uid@example.net should work

mfoss — Tue, 26 Jan 2010 09:25:52 +0000

Quote:

And the test user has a uid in the directory, do I use a username like "uid@example.net"?

Right. If that doesn't work, sniff the traffic (using a program like Ethereal/Wireshark, or tcpflow) between ejabberd and the LDAP server, maybe this gives you some idea where is the problem.

I think I've got that

colemanm — Tue, 26 Jan 2010 02:04:38 +0000

I think I've got that configured now...

{ldap_encrypt, none}.
{ldap_port, 389}.

When I tail /var/log/ejabberd/ejabberd.log, I repeated connections to the LDAP server, about once a second. And they look like successful connections. My issue now is logging in with an actual user account in my Jabber client. I guess I also don't understand what username I use to login from the client. Do the Jabber "hostnames" in the config file still apply, since Jabber is now taking over authentication?

If I have hostnames in config like this:

{hosts, ["example.net"]}.

And the test user has a uid in the directory, do I use a username like "uid@example.net"?

I'm trying that in Adium, and it seems to be seeing the server, but repeatedly asking for a password... I see nothing in the ejabberd log that looks suspicious...

Add: {ldap_encrypt, none}.

mfoss — Fri, 22 Jan 2010 12:25:26 +0000

Sometime in the past you had this option:

{ldap_encrypt, tls}.

Later you removed it from the config file, but it is remembered in the ejabberd internal database.

Better say explicitly you don't want to use encryption:

{ldap_encrypt, none}.