RE: SASL MD5 - another try

["Chapman, Kyle" <Kyle_Chapman@G1.com>]

you can store sasl stuff in ldap:

http://www.openldap.org/doc/admin21/sasl.html

-----Original Message-----
From: Dieter Kluenter [mailto:dieter@dkluenter.de]
Sent: Wednesday, July 16, 2003 10:11 AM
To: openldap-software@OpenLDAP.org
Subject: Re: SASL MD5 - another try


Hi,

Alexander Lunyov <lan_mailing@startatom.ru> writes:

> Hello openldap-software,
>
>   I'm still don't get it. Let's play it step by step.
>
>   1. Install Cyrus-SASL 2.1.13 with default options in configure (not
me,
>      it's port in FreeBSD).
>   2. Install OpenLDAP 2.1.21 with --enable-sasl option in configure
>      (also port).
>   3. Configure slapd.conf and add proper sasl-regexp option.
>   4. Get LDAP database filled.
>   5. Then i'm trying to bind to LDAP with -Y DIGEST-MD5 and result
same as before
>      - logs are growing fast with "daemon: select timeout - yielding"
>      entry. And that's all.
>
>   I dreaming to get some error that you people have - but i've got
>   only that "select timeout" and nobody seems to know what is
>   happening.
>
>   The questions are:
>
>   1. Is SASL really works with LDAP (stupid question? i don't think
so)?
>   2. Do i need to config SASL in some way?
>   3. Do i need to compile ldapdb auxprop plugin for SASL?
>   4. Can anyone if you have SASL & LDAP working together write some
>      small step by step howto?

You have to add users and password to sasldb.
saslpasswd2 -a ldap -u <sasl-realm> -c <user>

-Dieter
-- 
Dieter Kluenter  | Systemberatung
Tel:040.64861967 | Fax: 040.64891521
mailto: dkluenter(at)dkluenter.de
http://www.avci.de
NOTICE: This E-mail may contain confidential information. If you are not
the addressee or the intended recipient please do not read this E-mail
and please immediately delete this e-mail message and any attachments
from your workstation or network mail system. If you are the addressee
or the intended recipient and you save or print a copy of this E-mail,
please place it in an appropriate file, depending on whether
confidential information is contained in the message.