LDAP

Hey Guys,

I can't seem to get the connection to my LDAP working. Is there something special, that I have to think of?
When I try to connect, eJabberD tells me: "Failed legacy authentification for karsten.jahn@foo.de/Work"
One Problem may be, that our LDAP listens at a port that differs from standard. How can I figure that out?

The specific part of my config looks like this:
% For LDAP authentification use these lines instead of above one:
{auth_method, ldap}.
{ldap_servers, ["server.foo-intern.de"]}. % List of LDAP servers
{ldap_uidattr, "CN"}. % LDAP attribute that holds user ID
{ldap_base, "dc=foo-intern,dc=de"}. % Base of LDAP directory

% Host name:
{host, "foo.de"}.

Thanks in advance,
Karsten

LDAP?

I was wrong, it's on standard port.
Does anyone have a LDAP connection working? If so, how?!

eJabberD with IBM Lotus Domino LDAP

Anybody was got IBM Lotus Domino LDAP + eJabberD ?

Yes

ldap

the configuration is like this:

{auth_method, ldap}.
{ldap_servers, ["xx.xx.xx.xx"]}.% X is a ip address
{ldap_uidattr, "uid"}.
{ldap_rootdn, "cn=user,ou=group,o=domain"}. % UID complete of user
{ldap_base, "ou=group,o=domain"}. % zone of search
{ldap_password, "xxxxxxx"}. % X= is a password in text plain

but it does not work to me

Re: ldap

emergrin wrote:

{ldap_servers, ["10.120.55.123"]}.% X is a ip address
...

but it does not work to me

Try to put the hostname. If you only can use the IP address, maybe this works (I doubt, but you loose nothing trying):

{ldap_servers, [{10, 120, 55, 123}]}.

ldap

thank, but I does not work....... I use a hostname and does not work.

LDAP

the correct configuration is:

{auth_method, ldap}.
{ldap_servers, ["X"]}. %is a IP or Domain Name from LDAP server
{ldap_uidattr, "uid"}.
{ldap_rootdn, "cn=user,ou=group,o=domain"}.% user conect to LDAP
{ldap_base, "ou=group,o=domain"}. % search zone
{ldap_password, "X"}. %X password of user, in text plain

I have proven it and works, use user@node to conect.

The node must be equal to the Domain of LDAP

working ldap config

Hello,

I've just managed to authenticate my jabber users using an ldap directory server.
I'm using the testing package from debian (ejabberd 0.9.8-1) and a replica of my directory server on the jabber host (slapd 2.2.23-8).

For the moment i'm using the default config file with only those modifications :
%{auth_method, internal}.
{auth_method, ldap}.
{ldap_servers, ["localhost"]}.
{ldap_uidattr, "uid"}.
{ldap_base, "ou=Organisation,dc=sub,dc=domain,dc=tld"}.
{ldap_rootdn, "cn=login,dc=sub,dc=domain,dc=tld"}.
{ldap_password, "password"}.
{hosts, ["sub.domain.tld"]}.

login/password **must** be the admin of the directory server :(
It did not work for me using a non privileged account (that's why i've set up a replica : i don't want to connect the main server with its admin account accross the network).

the ldap base is the one that contains my users. if you have multiple OU, be carefull that not specifying the good one may result in multiple response when searching for a particular UID. then authentication may not work depending on which enry is found first.

I've also set up SRV DNS records but the client i've used to test my config did not seem to support it so that i had to specify the server name beside my user and domain.

I'm not sure but if the node should match the directory base address but that's the case in my configuration.

Hope these informations will help ...

Regards.

Syndicate content