[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: embeded ldap client ?

To: "Andreas Back" <Andreas.Back@comsel.com>
Subject: Re: embeded ldap client ?
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Date: Mon, 15 Jan 2001 11:00:56 -0800
Cc: <openldap-software@OpenLDAP.org>
In-reply-to: <sa5c2671.068@ms.comsel.fi>

At 09:07 AM 1/10/01 +0200, Andreas Back wrote:
>Have I understood the source right when I think I only 
>need to port libbeer and libldap for client functionality ??

To have a complete client LDAPv3 API, you need to port
        -lldap (libldap) -llber (liblber)

as well as Cyrus SASL.  Cyrus SASL is required for
SASL/DIGEST-MD5 functionality, LDAP's mandatory-to-implement
secure authentication mechanism (RFC2829).  You may also
want to port OpenSSL if you desire Transport Layer Security
(TLS) functionality (RFC 2830).

Kurt

References:
- embeded ldap client ?
  - From: "Andreas Back" <Andreas.Back@comsel.com>

Prev by Date: Re: Open Ldap closed !
Next by Date: RE: passwd.c and crypt
Index(es):
- Chronological
- Thread