Survey of available LDAP implementations

Mark Wahl (
Mon, 19 Aug 1996 21:06:49 -0500

This message is a call for submissions to a catalogue of LDAP
implementations. I am sorry if any of you get too many copies of this
message, for it is going to several distribution lists.

The catalogue is intended to be a listing of all available implementations
of the LDAP protocol and applications using it, including commercial products
and openly available offerings. This will provide information that will be
useful for those planning to deploy LDAP-based systems, in determining the
available implementations and whether these implementations would be

The catalogue is expected to be available around September 30, 1996. It will
be published to the mailing list, and made available on the Web
at the URL "". If there is
interest and additional submissions, the catalogue will continue to be revised
after that date.

If you have or are pursuing implementation of an LDAP library, client,
server or gateway which you wish to have included, please respond to
<> by September 20, 1996 with the attached form, to
be included in the first listing. If you have multiple independent products
which have distinct features (e.g. a basic browsing client product, and a more
powerful administration client product), please complete one form for each,
and be sure to indicate in 1.1 that they are distinct.

Also please let me know if you have any comments or questions on this form.

Thanks in advance,

Mark Wahl, Enterprise Directory Integration
Critical Angle Incorporated

=================================== BEGIN ===================================

Subject: survey response from [your name here] for [implementation name]

Survey of available LDAP implementations (Version of August 19, 1996)


1. Implementation Name and Contact Information

Please complete the following information so that we can identify company or
organization name, implementation name, and the name, postal address, e-mail
address, and telephone number of the contact person for this implementation.

1.1 Implementation short name or abbreviation:

1.2 Full Implementation Name:

1.3 URL of a Web page describing the implementation:

1.4 Contact Person:

1.5 Contact Person's E-mail Address:

1.6 Contact Person's Telephone Number:

1.7 Company or Organization Name:

1.8 Postal Address:


2. Description

2.1 Please provide a brief (less than a page) description of the


3. Implementation Type

3.1 Includes a Client (Y/N):

3.1.1 Does the Client have a graphical user interface (Y/N):

3.1.2 Client supports LDAP URLs (RFC 1959) (Y/N):

3.1.3 Client is part of a larger application (Y/N): Type of application (e.g. mail user agent):

3.2 Includes a Client-side library and API (Y/N):

3.2.1 Library API is as described in RFC 1823 (Y/N):

3.3 Includes a Server (Y/N):

3.3.1 Does the server master data (Y/N):

3.3.2 Does the server provide support for accessing data in existing
databases or repositories (Y/N):

3.3.3 Does the server provide support for contacting other servers (Y/N):

3.3.4 Any other protocols supported in server, such as DAP:

3.3.5 Server is part of a larger application (Y/N): Type of application (e.g. mail server):

3.4 Includes a Gateway _to_ LDAP (Y/N):

3.4.1 Supported protocols/applications (e.g. HTTP):

3.5 Includes a Gateway _from_ LDAP (Y/N):

3.5.2 Supported protocols/applications (e.g. DAP):

3.6 Other kind of component included:

3.7 Is the protocol implementation substantially derived from the
Umich release? (Y/N):

3.8 Please describe any particular environment or application for which this
implementation is tailored (e.g. email address lookup):


4. LDAP Conformance and Supported Features

4.1 Implements RFC 1777 (LDAPv2 protocol) (Y/N):

4.2 Implements RFC 1798 (CLDAP) (Y/N)

4.3 Transport protocols other than TCP and UDP supported:

4.4 Supports simple password-based authentication (Y/N):

4.5 Supports Kerberos authentication (Y/N):

4.6 Any other security mechanism (e.g. SSL):

4.7 Supports Search operation (Y/N):

4.7.1 Supports or uses inequality filters in searches (Y/N):

4.7.2 Supports or uses substrings filter for string attributes (Y/N):

4.7.3 Supports or uses approximate matching in filter (Y/N): If server, approximate match algorithm (e.g. SOUNDEX):

4.8 Supports Abandon operation (Y/N)

4.9 Supports Compare operation (Y/N):

4.10 Supports Modify operation (Y/N):

4.10.1 Supports modifications to the objectClass attribute (Y/N):

4.11 Supports Add and Remove operations (Y/N):

4.12 Supports ModifyRDN operation (Y/N):

4.13 Supports aliases (Y/N):

4.14 Supports all attributes defined in X.520(1988) (Y/N):

4.15 Supports all object classes defined in X.521(1988) (Y/N):

4.16 Supports all attributes and object classes of RFC 1274 (Y/N):

4.17 Supports additional attributes and object classes of X.500(1993) (Y/N):

4.18 If server, able to support collective attributes (Y/N):

4.19 Other attributes and object classes supported:

4.20 Permits administrators/users to add other attributes and object classes

4.21 Supports certificate and revocation list syntaxes (Y/N):

4.22 Supports Fax Photo, JPEG and Audio syntaxes (Y/N):

4.23 Supports all other syntaxes in RFC 1778 (Y/N):

4.24 Other syntaxes supported:

4.25 Permits administrators/users to add other syntaxes (Y/N):

4.26 Supports access control (Y/N):

4.26.1 Access control may be modified as attributes over protocol (Y/N):

4.26.2 Access control is QUIPU-compatible acl (Y/N):

4.26.3 Access control conforms to X.501(1993) Basic and/or Simplified (Y/N):

4.26.4 Other access control mechanism:

4.27 If client or client library, able to configure multiple
server addresses in case one is down (Y/N):

4.28 If client or client library, able to handle Umich LDAP 3.3 referrals

4.29 If server, generates Umich 3.3 referrals (Y/N):

4.30 If server, any supported replication protocols (e.g. DISP, getEDB):

4.31 Any nonstandard features required of peer client or server:

4.32 Other implementations with which known to interoperate:

4.33 Intend to upgrade implementation to support any LDAPv3 features,
as soon as LDAPv3 specifications are standards-track and a
reference implementation is available (Y/N):

4.33.1 particular features of LDAPv3 (e.g. extensions, referrals, security):

4.33.2 Any features which are not currently addressed in
LDAPv3 protocool specifications:

4.33.3 Plan to make use of LDAPv3 extended operations (Y/N):


5. Operating Environment

5.1 Implementation is provided in source form (Y/N):
5.1.1 Language (e.g. C):

5.2 Supported Operating Systems
5.2.1 MS-DOS (Y/N):
5.2.2 Microsoft Windows 3.X (Y/N):
5.2.3 Microsoft Windows 95 (Y/N):
5.2.4 Microsoft Windows NT (Y/N):
5.2.5 DEC ULTRIX (Y/N):
5.2.6 DEC UNIX (Y/N):
5.2.7 SunOS 4 (Y/N):
5.2.8 SunOS 5 (Y/N):
5.2.9 Generic UNIX with sockets and/or streams (Y/N):
5.2.10 Generic Java-capable (Y/N):
5.2.11 others (please list):

5.3 Supported Hardware Platforms, if platform-specific
5.3.1 Intel-based platform. 80386 - (Y/N): 80486 - (Y/N): Pentium-class (Y/N):
5.3.2 Bull (Y/N):
5.3.3 CDC MIPS (Y/N):
5.3.4 DEC AXP running OpenVMS (Y/N):
5.3.5 DEC VAX running OpenVMS (Y/N):
5.3.6 HP (Y/N):
5.3.7 IBM's RISC UNIX workstation (Y/N):
5.3.8 ICL (Y/N):
5.3.9 Macintosh (Y/N):
5.3.10 Sequent (Y/N):
5.3.11 Siemens Nixdorf (Y/N):
5.3.12 Solbourne (Y/N):
5.3.13 Tandem (Y/N):
5.3.14 Wang RISC (Y/N):
5.3.15 others (please list):


6. Availability

6.1 Implementation is now or will be available as of September 30, 1996 (Y/N):

6.2 Date of first availability:

6.3 Implementation is available using anonymous FTP or HTTP (Y/N):

6.3.1 If so, URL of distribution source:

6.4 This implementation can be purchased (Y/N):

6.5 Available at no charge, although other restrictions may apply (Y/N):

6.6 Need to contact provider for terms and conditions of distribution (Y/N):


Thanks for your time in completing this survey.
Please return to before September 20, 1996.

=================================== END ===================================