The following worked in our org--the part that made the difference was changing [ldap_uidattr] to "samAccountName"
Once I did that, it worked like a charm!
Hope this helps someone else
I've xxx out sensitive stuff.
Jennifer
% For LDAP authentification use these lines instead of above one:
{auth_method, ldap}.
{ldap_servers, ["xxx.xxx.xxx.xxx"]}. % List of LDAP servers
{ldap_uidattr, "samAccountName"}. % LDAP attribute that holds user ID
{ldap_base, "dc=xxx,dc=xxx,dc=edu"}. % Base of LDAP directory
{ldap_rootdn, "CN=xxx,OU=xxx,DC=xxx,DC=xxx,DC=edu"}.
{ldap_password, "xxx"}.
***************
Hi everyone
I've just setup ejabberd .91 on our windows 2003 server. I run the server and then try to connect. I get a message saying the server is listening, but I always get "authentication failure" on the client.
This is what I get on ERlang (i've blotted out the IPs)
=INFO REPORT==== 13-Jun-2005::09:56:48 ===
I(<0.254.0>:ejabberd_listener:89): (#Port<0.390>) Accepted connection {{192,168,
xxx,xxxx},2583} -> {{192,168,xxx,xxx},5222}
so it appears to be working...
Here is my ldap info--I've changed the server name and Ldap base stuff. I added ldap_rootdn and ldap_password as was suggested in another part of the forum.
% For LDAP authentification use these lines instead of above one:
{auth_method, ldap}.
{ldap_servers, ["ldapserver"]}. % List of LDAP servers
{ldap_uidattr, "uid"}. % LDAP attribute that holds user ID
{ldap_base, "dc=name,dc=name,dc=edu"}. % Base of LDAP directory
{ldap_rootdn, ""}.
{ldap_password, ""}.
any advice would be most appreciated.
Thanks!
Jennifer
