1 .TH SLAPD.CONF 5 "26 January 2002" "OpenLDAP LDVERSION"
2 .\" Copyright 1998-2002 The OpenLDAP Foundation All Rights Reserved.
3 .\" Copying restrictions apply. See COPYRIGHT/LICENSE.
6 slapd.conf \- configuration file for slapd, the stand-alone LDAP daemon
12 contains configuration information for the
14 daemon. This configuration file is also used by the
16 replication daemon and by the SLAPD tools
24 file consists of a series of global configuration options that apply to
26 as a whole (including all backends), followed by zero or more database
27 backend definitions that contain information specific to a backend
35 # comment - these options apply to every database
36 <global configuration options>
37 # first database definition & configuration options
38 database <backend 1 type>
39 <configuration options specific to backend 1>
40 # subsequent database definitions & configuration options
44 As many backend-specific sections as desired may be included. Global
45 options can be overridden in a backend (for options that appear more
46 than once, the last appearance in the
48 file is used). Blank lines and comment lines beginning with a `#'
49 character are ignored. If a line begins with white space, it is
50 considered a continuation of the previous line.
52 Arguments on configuration lines are separated by white space. If an
53 argument contains white space, the argument should be enclosed in
54 double quotes. If an argument contains a double quote (`"') or a
55 backslash character (`\\'), the character should be preceded by a
58 The specific configuration options available are discussed below in the
59 Global Configuration Options, General Backend Options, General Database
60 Options, LDBM Database-Specific Options,
61 Shell Database-Specific Options, and Password
62 Database-Specific Options sections. Refer to the "OpenLDAP
63 Administrator's Guide" for more details on the slapd configuration
65 .SH GLOBAL CONFIGURATION OPTIONS
66 Options described in this section apply to all backends, unless specifically
67 overridden in a backend definition. Arguments that should be replaced by
68 actual text are shown in brackets <>.
70 .B access to <what> [ by <who> <access> <control> ]+
71 Grant access (specified by <access>) to a set of entries and/or
72 attributes (specified by <what>) by one or more requestors (specified
74 See the "OpenLDAP's Administrator's Guide" for details.
77 Specify a set of features (separated by white space) to
80 allows acceptance of LDAPv2 bind requests.
82 allows anonymous bind when credentials are not empty (e.g.
85 allows unauthenticated (anonymous) bind when DN is not empty.
87 .B argsfile <filename>
88 The ( absolute ) name of a file that will hold the
90 server's command line options
91 if started without the debugging command line option.
94 .B attributetype (\ <oid> [NAME\ <name>] [OBSOLETE]\
95 [DESC\ <description>]\
96 [SUP\ <oid>] [EQUALITY\ <oid>] [ORDERING\ <oid>]\
97 [SUBSTR\ <oid>] [SYNTAX\ <oidlen>] [SINGLE\-VALUE] [COLLECTIVE]\
98 [NO\-USER\-MODIFICATION] [USAGE\ <attributeUsage>]\ )
100 Specify an attribute type using the LDAPv3 syntax defined in RFC 2252.
101 The slapd parser extends the RFC 2252 definition by allowing string
102 forms as well as numeric OIDs to be used for the attribute OID and
103 attribute syntax OID.
106 description.) Currently the syntax name parser is case-sensitive.
107 The known syntax names are:
111 AttributeTypeDescription Audio Binary BitString Certificate CertificateList
112 CertificatePair DN DeliveryMethod DirectoryString DITContentRuleDescription
113 DITStructureRuleDescription EnhancedGuide FacsimileTelephoneNumber
114 GeneralizedTime Guide IA5String Integer MatchingRuleDescription
115 MatchingRuleUseDescription MailPreference NameAndOptionalUUID
116 NameFormDescription NumericString ObjectClassDescription OID
117 OtherMailbox OctetString PostalAddress ProtocolInformation
118 PresentationAddress PrintableString SupportedAlgorithm TelephoneNumber
119 TeletexTerminalIdentifier TelexNumber UTCTime LDAPSyntaxDescription
120 SubstringAssertion NISnetgrouptriple Bootparameter
126 .B concurrency <integer>
127 Specify a desired level of concurrency. Provided to the underlying
128 thread system as a hint. The default is not to provide any hint.
130 .B defaultsearchbase <dn>
131 Specify a default search base to use when client submits a
132 non-base search request with an empty base DN.
134 .B disallow <features>
135 Specify a set of features (separated by white space) to
136 disallow (default none).
138 disables acceptance of anonymous bind requests.
140 disables simple (bind) authentication.
142 disables Kerberos V4 (bind) authentication.
144 disables Start TLS from forcing session to anonymous status (see also
147 disables StartTLS if authenticated (see also
150 .B idletimeout <integer>
151 Specify the number of seconds to wait before forcibly closing
152 an idle client connection. A idletimeout of 0 disables this
153 feature. The default is 0.
155 .B include <filename>
156 Read additional configuration information from the given file before
157 continuing with the next line of the current file.
159 .B limits <who> <limit> [<limit> [...]]
160 Specify time and size limits based on who initiated an operation.
167 anonymous | users | [dn[.<style>]=]<pattern>
173 <style> ::= exact | base | one | subtree | children | regex | anonymous
177 is hit when a search is performed without prior binding;
179 is hit when a search is performed by a successfully bound user;
182 dn pattern is assumed unless otherwise specified by qualifying
183 the (optional) key string
189 (which are synonims), to require an exact match; with
191 to require exactly one level of depth match; with
193 to allow any level of depth match, including the exact match; with
195 to allow any level of depth match, not including the exact match;
197 explicitly requires the (default) match based on regular expression
198 pattern, as detailed in
202 matches unbound operations; the
205 The same behavior is obtained by using the
211 The currently supported limits are
216 The syntax for time limits is
217 .BR time[.{soft|hard}]=<integer> ,
220 is the number of seconds slapd will spend answering a search request.
221 If no time limit is explicitly requested by the client, the
223 limit is used; if the requested time limit exceedes the
225 limit, an "Unwilling to perform" is returned.
228 limit is set to 0 or to the keyword "soft", the soft limit is used
229 in either case; if it is set to -1 or to the keyword "none",
230 no hard limit is enforced.
231 Explicit requests for time limits smaller or equal to the
234 If no flag is set, the value is assigned to the
238 limit is set to zero, to preserve the original behavior.
240 The syntax for size limits is
241 .BR size[.{soft|hard|unchecked}]=<integer> ,
244 is the maximum number of entries slapd will return answering a search
246 If no size limit is explicitly requested by the client, the
248 limit is used; if the requested size limit exceedes the
250 limit, an "Unwilling to perform" is returned.
253 limit is set to 0 or to the keyword "soft", the soft limit is used
254 in either case; if it is set to -1 or to the keyword "none",
255 no hard limit is enforced.
256 Explicit requests for size limits smaller or equal to the
261 flag sets a limit on the number of candidates a search request is allowed
263 If the selected candidates exceed the
265 limit, the search will abort with "Unwilling to perform".
266 If it is set to -1 or to the keyword "none", no limit is applied (the default).
267 If no flag is set, the value is assigned to the
271 limit is set to zero, to preserve the original behavior.
273 In case of no match, the global limits are used.
274 The default values are the same of
282 .B loglevel <integer>
283 Specify the level at which debugging statements and operation
284 statistics should be syslogged (currently logged to the
286 LOG_LOCAL4 facility). Log levels are additive, and available levels
296 debug packet handling
299 heavy trace debugging
302 connection management
305 print out packets sent and received
308 search filter processing
311 configuration file processing
314 access control list processing
317 stats log connections/operations/results
320 stats log entries sent
323 print communication with shell backends
331 .B objectclass ( <oid> [NAME <name>] [DESC <description] [OBSOLETE]\
332 [SUP <oids>] [{ ABSTRACT | STRUCTURAL | AUXILIARY }] [MUST <oids>]\
335 Specify an objectclass using the LDAPv3 syntax defined in RFC 2252.
336 The slapd parser extends the RFC 2252 definition by allowing string
337 forms as well as numeric OIDs to be used for the object class OID.
341 description.) Object classes are "STRUCTURAL" by default.
344 .B objectidentifier <name> { <oid> | <name>[:<suffix>] }
345 Define a string name that equates to the given OID. The string can be used
346 in place of the numeric OID in objectclass and attribute definitions. The
347 name can also be used with a suffix of the form ":xx" in which case the
348 value "oid.xx" will be used.
350 .B password-hash <hash>
351 This option sets the hash to be used in generation of user
352 passwords, stored in userPassword, during processing of
353 LDAP Password Modify Extended Operations (RFC 3052).
354 The <hash> must be one of
364 Note that this option does not alter the normal user applications
365 handling of userPassword during LDAP Add, Modify, or other LDAP operations.
367 .B password\-crypt\-salt\-format <format>
368 Specify the format of the salt passed to
370 when generating {CRYPT} passwords (see
372 during processing of LDAP Password Modify Extended Operations (RFC 3062).
374 This string needs to be in
376 format and may include one (and only one) %s conversion.
377 This conversion will be substituted with a string random
378 characters from [A\-Za\-z0\-9./]. For example, "%.2s"
379 provides a two character salt and "$1$%.8s" tells some
380 versions of crypt(3) to use an MD5 algorithm and provides
381 8 random characters of salt. The default is "%s", which
382 provides 31 characters of salt.
384 .B pidfile <filename>
385 The ( absolute ) name of a file that will hold the
387 server's process ID ( see
389 ) if started without the debugging command line option.
392 Specify the referral to pass back when
394 cannot find a local database to handle a request.
395 If specified multiple times, each url is provided.
397 .B require <conditions>
398 Specify a set of conditions (separated by white space) to
399 require (default none).
400 The directive may be specified globally and/or per-database.
402 requires bind operation prior to directory operations.
404 requires session to be using LDAP version 3.
406 requires authentication prior to directory operations.
408 requires SASL authentication prior to directory operations.
410 requires strong authentication prior to directory operations.
415 conditions are currently same.
417 may be used to require no conditions (useful for clearly globally
418 set conditions within a particular database).
420 .B reverse-lookup on | off
421 Enable/disable client name reverse lookup (default is
423 if compiled with --enable-rlookups).
426 Specify the name of an LDIF(5) file containing user defined attributes
427 for the root DSE. These attributes are returned in addition to the
428 attributes normally produced by slapd.
431 Used to specify the fully qualified domain name used for SASL processing.
433 .B sasl-realm <realm>
434 Specify SASL realm. Default is empty.
436 .B sasl-regexp <match> <replace>
437 Used by the SASL authorization mechanism to convert a SASL authenticated
438 username to an LDAP DN. When an authorization request is received, the SASL
442 are taken, when available, and combined into a SASL name of the
447 .B uid=<UID>[,cn=<REALM>][,cn=<MECH>],cn=AUTHZ
450 This SASL name is then compared against the
452 regular expression, and if the match is successful, the SASL name is
455 string. If there are wildcard strings in the
457 regular expression that are enclosed in parenthesis, e.g.
461 .B uid=(.*)\\\\+realm=.*
465 then the portion of the SASL name that matched the wildcard will be stored
466 in the numbered placeholder variable $1. If there are other wildcard strings
467 in parenthesis, the matching strings will be in $2, $3, etc. up to $9. The
468 placeholders can then be used in the
474 .B cn=$1,ou=Accounts,dc=$2,dc=$4.
478 The replaced SASL name can be either a DN or an LDAP URI. If the latter, the slapd
479 server will use the URI to search its own database, and if the search returns
480 exactly one entry, the SASL name is replaced by the DN of that entry.
483 options can be given in the configuration file to allow for multiple matching
484 and replacement patterns. The matching patterns are checked in the order they
485 appear in the file, stopping at the first successful match.
488 Because the plus sign + is a character recognized by the regular expression engine,
489 and it will appear in SASL names that include a REALM, be careful to escape the
490 plus sign with a backslash \\+ to remove the character's special meaning.
493 .B sasl-secprops <properties>
494 Used to specify Cyrus SASL security properties.
497 flag (without any other properities) causes the flag properites
498 default, "noanonymous,noplain", to be cleared.
501 flag disables mechanisms susceptible to simple passive attacks.
504 flag disables mechanisms susceptible to active attacks.
507 flag disables mechanisms susceptible to passive dictionary attacks.
510 flag disables mechanisms which support anonymous login.
513 flag require forward secrecy between sessions.
516 require mechanisms which pass client credentials (and allow
517 mechanisms which can pass credentials to do so).
520 property specifies the minimum acceptable
521 .I security strength factor
522 as an integer approximate to effective key length used for
523 encryption. 0 (zero) implies no protection, 1 implies integrity
524 protection only, 56 allows DES or other weak ciphers, 112
525 allows triple DES and other strong ciphers, 128 allows RC4,
526 Blowfish and other modern strong ciphers. The default is 0.
529 property specifies the maximum acceptable
530 .I security strength factor
531 as an integer (see minssf description). The default is INT_MAX.
534 property specifies the maximum security layer receive buffer
535 size allowed. 0 disables security layers. The default is 65536.
537 .B security <factors>
538 Specify a set of factors (separated by white space) to require.
539 An integer value is associated with each factor and is roughly
540 equivalent of the encryption key length to require. A value
541 of 112 is equivalent to 3DES, 128 to Blowfish, etc..
542 The directive may be specified globally and/or per-database.
544 specifies the overall security strength factor.
546 specifies the transport security strength factor.
548 specifies the TLS security strength factor.
550 specifies the SASL security strength factor.
552 specifies the overall security strength factor to require for
554 .B update_transport=<n>
555 specifies the transport security strength factor to require for
558 specifies the TLS security strength factor to require for
561 specifies the SASL security strength factor to require for
565 factor is measure of security provided by the underlying transport,
566 e.g. ldapi:// (and eventually IPSEC). It is not normally used.
568 .B sizelimit <integer>
570 .B sizelimit size[.{soft|hard|unchecked}]=<integer> [...]
571 Specify the maximum number of entries to return from a search operation.
572 The default size limit is 500.
573 The second format allows a fine grain setting of the size limits.
574 Extra args can be added on the same line.
577 for an explanation of the different flags.
579 .B sockbuf_max_incoming <integer>
580 Specify the maximum incoming LDAP PDU size for anonymous sessions.
581 The default is 262143.
583 .B sockbuf_max_incoming_auth <integer>
584 Specify the maximum incoming LDAP PDU size for authenticated sessions.
585 The default is 4194303.
588 Specify the srvtab file in which the kerberos keys necessary for
589 authenticating clients using kerberos can be found. This option is only
590 meaningful if you are using Kerberos authentication.
593 Specify the maximum size of the primary thread pool.
596 .B timelimit <integer>
598 .B timelimit time[.{soft|hard}]=<integer> [...]
599 Specify the maximum number of seconds (in real time)
601 will spend answering a search request. The default time limit is 3600.
602 The second format allows a fine grain setting of the time limits.
603 Extra args can be added on the same line.
606 for an explanation of the different flags.
610 is built with support for Transport Layer Security, there are more options
613 .B TLSCipherSuite <cipher-suite-spec>
614 Permits configuring what ciphers will be accepted and the preference order.
615 <cipher-suite-spec> should be a cipher specification for OpenSSL. Example:
617 TLSCipherSuite HIGH:MEDIUM:+SSLv2
619 To check what ciphers a given spec selects, use:
621 openssl ciphers -v <cipher-suite-spec>
623 .B TLSCACertificateFile <filename>
624 Specifies the file that contains certificates for all of the Certificate
629 .B TLSCertificateFile <filename>
630 Specifies the file that contains the
634 .B TLSCertificateKeyFile <filename>
635 Specifies the file that contains the
637 server private key that matches the certificate stored in the
638 .B TLSCertificateFile
639 file. Currently, the private key must not be protected with a password, so
640 it is of critical importance that it is protected carefully.
642 .B TLSRandFile <filename>
643 Specifies the file to obtain random bits from when /dev/[u]random
644 is not available. Generally set to the name of the EGD/PRNGD socket.
645 The environment variable RANDFILE can also be used to specify the filename.
647 .B TLSVerifyClient <level>
648 Specifies what checks to perform on client certificates in an
649 incoming TLS session, if any.
652 can be specified as one of the following keywords:
658 will not ask the client for a certificate.
661 The client certificate is requested. If no certificate is provided,
662 the session proceeds normally. If a bad certificate is provided,
663 it will be ignored and the session proceeds normally.
666 The client certificate is requested. If no certificate is provided,
667 the session proceeds normally. If a bad certificate is provided,
668 the session is immediately terminated.
670 .B demand | hard | true
671 These keywords are all equivalent, for compatibility reasons.
672 The client certificate is requested. If no certificate is provided,
673 or a bad certificate is provided, the session is immediately terminated.
675 Note that a valid client certificate is required in order to use the
676 SASL EXTERNAL authentication mechanism with a TLS session. As such,
679 setting must be chosen to enable SASL EXTERNAL authentication.
681 .SH GENERAL BACKEND OPTIONS
682 Options in this section only apply to the configuration file section
683 for the specified backend. They are supported by every
686 .B backend <databasetype>
687 Mark the beginning of a backend definition. <databasetype>
702 depending on which backend will serve the database.
704 .SH GENERAL DATABASE OPTIONS
705 Options in this section only apply to the configuration file section
706 for the database in which they are defined. They are supported by every
709 .B database <databasetype>
710 Mark the beginning of a new database instance definition. <databasetype>
725 depending on which backend will serve the database.
730 will automatically maintain the
731 modifiersName, modifyTimestamp, creatorsName, and
732 createTimestamp attributes for entries. By default, lastmod is on.
735 This option puts the database into "read-only" mode. Any attempts to
736 modify the database will return an "unwilling to perform" error. By
737 default, readonly is off.
739 .B replica host=<hostname>[:port] [tls=yes|critical]
740 .B [suffix=<suffix> [...]]
741 .B bindmethod=simple|sasl [binddn=<simple DN>] [credentials=<simple password>]
742 .B [saslmech=<SASL mech>] [secopts=<options>] [realm=<realm>]
743 .B [authcId=<authentication ID>] [authcId=<authentication ID>]
744 .B [attr[!]=<attr list>]
746 Specify a replication site for this database. Refer to the "OpenLDAP
747 Administrator's Guide" for detailed information on setting up a replicated
749 directory service. Zero or more
751 instances can be used to select the subtrees that will be replicated
752 (defaults to all the database). A
760 and should only be used when adequate security services
761 (e.g TLS or IPSEC) are in place. A
769 will use Kerberos, a kerberos instance should be given in
773 can be given after the
775 keyword to allow the selective replication of the listed attributes only;
778 mark is used, the list is considered exclusive, i.e. the listed attributes
780 If an objectClass is listed, all the related attributes
781 are (are not) replicated.
784 .B replogfile <filename>
785 Specify the name of the replication log file to log changes to.
786 The replication log is typically written by
792 for more information. The specified file should be located
793 in a directory with limited read/write/execute access as the replication
794 logs may contain sensitive information.
797 Specify the distinguished name that is not subject to access control
798 or administrative limit restrictions for operations on this database.
799 This DN may or may not be associated with an entry. An empty root
800 DN (the default) specifies no root access is to be granted. It is
801 recommended that the rootdn only be specified when needed (such as
802 when initially populating a database). If the rootdn is within
803 a namingContext (suffix) of the database, a simple bind password
804 may also be provided using the
809 Specify a password (or hash of the password) for the rootdn. If
810 the rootdn is not within the namingContext of the database, the
811 provided password is ignored.
812 This option accepts all RFC 2307 userPassword formats known to
815 desription) as well as cleartext.
817 may be used to generate a hash of a password. Cleartext
818 and \fB{CRYPT}\fP passwords are not recommended. If empty
819 (the default), authentication of the root DN is by other means
820 (e.g. SASL). Use of SASL is encouraged.
822 .B suffix <dn suffix>
823 Specify the DN suffix of queries that will be passed to this
824 backend database. Multiple suffix lines can be given and at least one is
825 required for each database definition.
828 Specify that the current backend database is a subordinate of another
829 backend database. A subordinate database may have only one suffix. This
830 option may be used to glue multiple databases into a single namingContext.
831 If the suffix of the current database is within the namingContext of a
832 superior database, searches against the superior database will be
833 propagated to the subordinate as well. All of the databases
834 associated with a single namingContext should have identical rootdns.
835 Behavior of other LDAP operations is unaffected by this setting. In
836 particular, it is not possible to use moddn to move an entry from
837 one subordinate to another subordinate within the namingContext.
840 This option is only applicable in a slave
842 It specifies the DN allowed to make changes to the replica (typically,
845 binds as when making changes to the replica).
848 Specify the referral to pass back when
850 is asked to modify a replicated local database.
851 If specified multiple times, each url is provided.
852 .\" .SH LDBM BACKEND-SPECIFIC OPTIONS
853 .\" Options in this category only apply to the LDBM backend. That is,
854 .\" they must follow "backend ldbm" line and come before any subsequent
855 .\" "backend" or "database" lines. The LDBM backend is a high-performance
856 .\" database that makes extensive use of indexing and caching to speed
858 .SH BDB DATABASE-SPECIFIC OPTIONS
859 Options in this category only apply to the BDB databases. That is,
860 they must follow "database bdb" line and come before any subsequent
861 "backend" or "database" lines.
862 .SH LDBM DATABASE-SPECIFIC OPTIONS
863 Options in this category only apply to the LDBM databases. That is,
864 they must follow "database ldbm" line and come before any subsequent
865 "backend" or "database" lines.
867 .B cachesize <integer>
868 Specify the size in entries of the in-memory cache maintained
869 by the LDBM backend database instance. The default is 1000 entries.
871 .B dbcachesize <integer>
872 Specify the size in bytes of the in-memory cache associated
873 with each open index file. If not supported by the underlying database
874 method, this option is ignored without comment. The default is 100000 bytes.
877 Specify that no database locking should be performed.
878 Enabling this option may improve performance at the expense of data security.
879 Do NOT run any slap tools while slapd is running.
882 Specify that on-disk database contents should not be immediately
883 synchronized with in memory changes. Enabling this option may improve
884 performance at the expense of data security.
886 .B dbsync <frequency> <maxdelays> <delayinterval>
887 Flush dirty database buffers to disk every
891 (ie. indvidual updates are no longer written to disk). It attempts to avoid
892 syncs during periods of peak activity by waiting
894 seconds if the server is busy, repeating this delay up to
896 times before proceeding.
897 It is an attempt to provide higher write performance with some amount of data
898 security. Note that it may still be possible to get an inconsistent
899 database if the underlying engine fills its cache and writes out individual
900 pages and slapd crashes or is killed before the next sync.
904 are optional and default to
908 respectively, giving a total elapsed delay of 60 seconds before a sync
913 must be 1 or greater.
915 .B directory <directory>
916 Specify the directory where the LDBM files containing this database and
917 associated indexes live. A separate directory must be specified for
918 each database. The default is
919 .BR LOCALSTATEDIR/openldap-data .
922 index {<attrlist>|default} [pres,eq,approx,sub,<special>]
923 Specify the indexes to maintain for the given attribute (or
924 list of attributes). Some attributes only support a subset
925 of indexes. If only an <attr> is given, the indices specified
926 for \fBdefault\fR are maintained. Note that setting a default
927 does not imply that all attributes will be indexed.
929 A number of special index parameters may be
933 can be decomposed into
940 may be specified to disallow use of this index by language subtypes.
943 may be specified to disallow use of this index by named subtypes.
944 Note: changing index settings requires rebuilding indices, see
948 Specify the file protection mode that newly created database
949 index files should have. The default is 0600.
950 .SH SHELL DATABASE-SPECIFIC OPTIONS
951 Options in this category only apply to the SHELL backend database. That is,
952 they must follow a "database shell" line and come before any subsequent
953 "backend" or "database" lines. The Shell backend executes external programs to
954 implement operations, and is designed to make it easy to tie an existing
965 .B compare <pathname>
975 .B abandon <pathname>
976 These options specify the pathname of the command to execute in response
977 to the given LDAP operation.
979 Note that you need only supply configuration lines for those commands you
980 want the backend to handle. Operations for which a command is not
981 supplied will be refused with an "unwilling to perform" error.
982 .SH PASSWORD DATABASE-SPECIFIC OPTIONS
983 Options in this category only apply to the PASSWD backend database.
984 That is, they must follow a "database passwd" line and come before any
985 subsequent "backend" or "database" lines. The PASSWD database serves up the user
986 account information listed in the system
991 Specifies an alternate passwd file to use. The default is
993 .SH OTHER DATABASE-SPECIFIC OPTIONS
994 Other databases may allow specific configuration options; they will be
995 documented separately since most of these databases are very specific
998 "OpenLDAP Administrator's Guide" contains an annotated
999 example of a configuration file.
1004 .BR slapd.replog (5),
1005 .BR slapd.access (5),
1012 .BR slappassword (8),
1015 "OpenLDAP Administrator's Guide" (http://www.OpenLDAP.org/doc/admin/)
1016 .SH ACKNOWLEDGEMENTS
1018 is developed and maintained by The OpenLDAP Project (http://www.openldap.org/).
1020 is derived from University of Michigan LDAP 3.3 Release.