Hi!

I used to run an older jabberd2 release, I just upgraded to 2.1.18

I use a LDAP server for auth, and after the upgrade it seems I'm unable
to make users auth work anymore.

I compiled jabberd2 with debug flags, ldap support and berkeley DB support, and
start it with bin/jabberd -D

When trying to login from my remote jabber client, I get errors in the
debugging log:

C2S : Fri Oct 26 19:52:08 2007 [error] ldap: bind failed:
Confidentiality required realm: XXXXX.XX basedn: o=XXXXX,c=XXX binddn:
cn=XXXX,o=XXXXX,c=XX pass: XXXXXXXXX

I conclude LDAP complains the connection does not use encryption;
strange, as my ldap blurb in c2s.xml forces starttls :

<ldap>
        <host>XXX.XXX.XXX.XXX</host>
        <port>389</port>
        <v3/>
        <starttls/>
        <!-- <ssl/> -->
        <binddn>cn=root,o=XXXXX,c=XXX</binddn>
        <bindpw>XXXXXXXXXXXXXX</bindpw>
        <uidattr>cn</uidattr>
        <basedn>o=XXXXX,c=XX</basedn>
</ldap>

A test with the above credentials using `ldapsearch` works; as mentioned before
the jabber version I used before (named jabberd-2.0-0.s11.9 by Fedora) worked
perfectly.  I'm probably overlooking something that changed between the two
versions.  Anybody has a clue?



-- 
 --====|====--
    --------================|================--------
        Patrice Levesque
         http://ptaff.ca/
        [EMAIL PROTECTED]
    --------================|================--------
 --====|====--
--

Attachment: pgpULpgABf0sl.pgp
Description: PGP signature

_______________________________________________
Jabberd2 mailing list
[email protected]
http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com

Reply via email to