1 .TH SLAPD-CONFIG 5 "RELEASEDATE" "OpenLDAP LDVERSION"
2 .\" Copyright 1998-2007 The OpenLDAP Foundation All Rights Reserved.
3 .\" Copying restrictions apply. See COPYRIGHT/LICENSE.
6 slapd-config \- configuration backend to slapd
12 backend manages all of the configuration information for the
14 daemon. This configuration information is also used by the SLAPD tools
26 backend is backward compatible with the older
28 file but provides the ability to change the configuration dynamically
29 at runtime. If slapd is run with only a
31 file dynamic changes will be allowed but they will not persist across
32 a server restart. Dynamic changes are only saved when slapd is running
35 configuration directory.
38 Unlike other backends, there can only be one instance of the
40 backend, and most of its structure is predefined. The root of the
41 database is hardcoded to
43 and this root entry contains
44 global settings for slapd. Multiple child entries underneath the
45 root entry are used to carry various other settings:
49 dynamically loaded modules
55 backend-specific settings
58 database-specific settings
63 entries will only appear in configurations where slapd
64 was built with support for dynamically loaded modules. There can be
65 multiple entries, one for each configured module path. Within each
66 entry there will be values recorded for each module loaded on a
67 given path. These entries have no children.
71 entry contains all of the hardcoded schema elements.
72 The children of this entry contain all user-defined schema elements.
73 In schema that were loaded from include files, the child entry will
74 be named after the include file from which the schema was loaded.
75 Typically the first child in this subtree will be
76 .BR cn=core,cn=schema,cn=config .
79 entries are for storing settings specific to a single
80 backend type (and thus global to all database instances of that type).
81 At present there are no backends that implement settings of this
82 nature, so usually there will not be any olcBackend entries.
85 entries store settings specific to a single database
86 instance. These entries may have
88 child entries corresponding
89 to any overlays configured on the database. The olcDatabase and
90 olcOverlay entries may also have miscellaneous child entries for
91 other settings as needed. There are two special database entries
92 that are predefined - one is an entry for the config database itself,
93 and the other is for the "frontend" database. Settings in the
94 frontend database are inherited by the other databases, unless
95 they are explicitly overridden in a specific database.
97 The specific configuration options available are discussed below in the
98 Global Configuration Options, General Backend Options, and General Database
99 Options. Options are set by defining LDAP attributes with specific values.
100 In general the names of the LDAP attributes are the same as the corresponding
102 keyword, with an "olc" prefix added on.
104 The parser for many of these attributes is the same as used for parsing
105 the slapd.conf keywords. As such, slapd.conf keywords that allow multiple
106 items to be specified on one line, separated by whitespace, will allow
107 multiple items to be specified in one attribute value. However, when
108 reading the attribute via LDAP, the items will be returned as individual
111 Backend-specific options are discussed in the
112 .B slapd-<backend>(5)
113 manual pages. Refer to the "OpenLDAP Administrator's Guide" for more
114 details on configuring slapd.
115 .SH GLOBAL CONFIGURATION OPTIONS
116 Options described in this section apply to the server as a whole.
117 Arguments that should be replaced by
118 actual text are shown in brackets <>.
120 These options may only be specified in the
122 entry. This entry must have an objectClass of
126 .B olcAllows: <features>
127 Specify a set of features to allow (default none).
129 allows acceptance of LDAPv2 bind requests. Note that
131 does not truly implement LDAPv2 (RFC 1777), now Historic (RFC 3494).
133 allows anonymous bind when credentials are not empty (e.g.
136 allows unauthenticated (anonymous) bind when DN is not empty.
138 allows unauthenticated (anonymous) update operations to be processed
139 (subject to access controls and other administrative limits).
141 allows unauthenticated (anonymous) proxy authorization control to be processed
142 (subject to access controls, authorization and other administrative limits).
144 .B olcArgsFile: <filename>
145 The ( absolute ) name of a file that will hold the
147 server's command line options
148 if started without the debugging command line option.
150 .B olcAttributeOptions: <option-name>...
151 Define tagging attribute options or option tag/range prefixes.
152 Options must not end with `-', prefixes must end with `-'.
153 The `lang-' prefix is predefined.
155 .B olcAttributeOptions
156 directive, `lang-' will no longer be defined and you must specify it
157 explicitly if you want it defined.
159 An attribute description with a tagging option is a subtype of that
160 attribute description without the option.
161 Except for that, options defined this way have no special semantics.
162 Prefixes defined this way work like the `lang-' options:
163 They define a prefix for tagging options starting with the prefix.
164 That is, if you define the prefix `x-foo-', you can use the option
166 Furthermore, in a search or compare, a prefix or range name (with
167 a trailing `-') matches all options starting with that name, as well
168 as the option with the range name sans the trailing `-'.
169 That is, `x-foo-bar-' matches `x-foo-bar' and `x-foo-bar-baz'.
171 RFC 4520 reserves options beginning with `x-' for private experiments.
172 Other options should be registered with IANA, see RFC 4520 section 3.5.
173 OpenLDAP also has the `binary' option built in, but this is a transfer
174 option, not a tagging option.
176 .B olcAuthzPolicy: <policy>
177 Used to specify which rules to use for Proxy Authorization. Proxy
178 authorization allows a client to authenticate to the server using one
179 user's credentials, but specify a different identity to use for authorization
180 and access control purposes. It essentially allows user A to login as user
181 B, using user A's password.
184 flag disables proxy authorization. This is the default setting.
187 flag will use rules in the
189 attribute of the authorization DN.
192 flag will use rules in the
194 attribute of the authentication DN.
197 flag, an alias for the deprecated value of
199 will allow any of the above, whatever succeeds first (checked in
205 flag requires both authorizations to succeed.
208 The rules are mechanisms to specify which identities are allowed
209 to perform proxy authorization.
212 attribute in an entry specifies which other users
213 are allowed to proxy login to this entry. The
216 an entry specifies which other users this user can authorize as. Use of
219 abused if users are allowed to write arbitrary values to this attribute.
222 attribute must be protected with ACLs such that
223 only privileged users can modify it.
230 or a set of identities; it can take five forms:
233 .B ldap:///<base>??[<scope>]?<filter>
236 .B dn[.<dnstyle>]:<pattern>
239 .B u[<mech>[<realm>]]:<pattern>
242 .B group[/objectClass[/attributeType]]:<pattern>
249 .B <dnstyle>:={exact|onelevel|children|subtree|regex}
252 The first form is a valid LDAP
260 portions must be absent, so that the search occurs locally on either
266 with the optional style modifiers
272 for exact, onelevel, children and subtree matches, which cause
274 to be normalized according to the DN normalization rules, or the special
276 style, which causes the
278 to be treated as a POSIX (''extended'') regular expression, as
285 means any non-anonymous DN.
286 The third form is a SASL
288 with the optional fields
292 that allow to specify a SASL
294 and eventually a SASL
296 for those mechanisms that support one.
297 The need to allow the specification of a mechanism is still debated,
298 and users are strongly discouraged to rely on this possibility.
299 The fourth form is a group specification, consisting of the keyword
301 optionally followed by the specification of the group
307 is searched with base scope, and in case of match, the values of the
310 are searched for the asserted DN.
311 For backwards compatibility, if no identity type is provided, i.e. only
315 is assumed; as a consequence,
317 is subjected to DN normalization.
318 Since the interpretation of
322 can impact security, users are strongly encouraged
323 to explicitly set the type of identity specification that is being used.
324 A subset of these rules can be used as third arg in the
326 statement (see below); significantly, the
333 .B olcAuthzRegexp: <match> <replace>
334 Used by the authentication framework to convert simple user names,
335 such as provided by SASL subsystem, to an LDAP DN used for
336 authorization purposes. Note that the resultant DN need not refer
337 to an existing entry to be considered valid. When an authorization
338 request is received from the SASL subsystem, the SASL
343 are taken, when available, and combined into a name of the form
347 .B UID=<username>[[,CN=<realm>],CN=<mechanism>],CN=auth
350 This name is then compared against the
352 POSIX (''extended'') regular expression, and if the match is successful,
353 the name is replaced with the
355 string. If there are wildcard strings in the
357 regular expression that are enclosed in parenthesis, e.g.
363 then the portion of the name that matched the wildcard will be stored
364 in the numbered placeholder variable $1. If there are other wildcard strings
365 in parenthesis, the matching strings will be in $2, $3, etc. up to $9. The
366 placeholders can then be used in the
371 .B UID=$1,OU=Accounts,DC=example,DC=com
374 The replaced name can be either a DN, i.e. a string prefixed by "dn:",
376 If the latter, the server will use the URI to search its own database(s)
377 and, if the search returns exactly one entry, the name is
378 replaced by the DN of that entry. The LDAP URI must have no
379 hostport, attrs, or extensions components, but the filter is mandatory,
383 .B ldap:///OU=Accounts,DC=example,DC=com??one?(UID=$1)
386 The protocol portion of the URI must be strictly
388 Note that this search is subject to access controls. Specifically,
389 the authentication identity must have "auth" access in the subject.
393 values can be specified to allow for multiple matching
394 and replacement patterns. The matching patterns are checked in the order they
395 appear in the attribute, stopping at the first successful match.
398 .\"Because the plus sign + is a character recognized by the regular expression engine,
399 .\"and it will appear in names that include a REALM, be careful to escape the
400 .\"plus sign with a backslash \\+ to remove the character's special meaning.
403 .B olcConcurrency: <integer>
404 Specify a desired level of concurrency. Provided to the underlying
405 thread system as a hint. The default is not to provide any hint. This setting
406 is only meaningful on some platforms where there is not a one to one
407 correspondence between user threads and kernel threads.
409 .B olcConnMaxPending: <integer>
410 Specify the maximum number of pending requests for an anonymous session.
411 If requests are submitted faster than the server can process them, they
412 will be queued up to this limit. If the limit is exceeded, the session
413 is closed. The default is 100.
415 .B olcConnMaxPendingAuth: <integer>
416 Specify the maximum number of pending requests for an authenticated session.
419 .B olcDisallows: <features>
420 Specify a set of features to disallow (default none).
422 disables acceptance of anonymous bind requests. Note that this setting
423 does not prohibit anonymous directory access (See "require authc").
425 disables simple (bind) authentication.
427 disables forcing session to anonymous status (see also
429 upon StartTLS operation receipt.
431 disallows the StartTLS operation if authenticated (see also
434 .B olcGentleHUP: { TRUE | FALSE }
435 A SIGHUP signal will only cause a 'gentle' shutdown-attempt:
437 will stop listening for new connections, but will not close the
438 connections to the current clients. Future write operations return
439 unwilling-to-perform, though. Slapd terminates when all clients
440 have closed their connections (if they ever do), or \- as before \-
441 if it receives a SIGTERM signal. This can be useful if you wish to
442 terminate the server and start a new
445 .B with another database,
446 without disrupting the currently active clients.
447 The default is FALSE. You may wish to use
449 along with this option.
451 .B olcIdleTimeout: <integer>
452 Specify the number of seconds to wait before forcibly closing
453 an idle client connection. A setting of 0 disables this
454 feature. The default is 0.
456 .B olcIndexIntLen: <integer>
457 Specify the key length for ordered integer indices. The most significant
458 bytes of the binary integer will be used for index keys. The default
459 value is 4, which provides exact indexing for 31 bit values.
460 A floating point representation is used to index too large values.
462 .B olcIndexSubstrIfMaxlen: <integer>
463 Specify the maximum length for subinitial and subfinal indices. Only
464 this many characters of an attribute value will be processed by the
465 indexing functions; any excess characters are ignored. The default is 4.
467 .B olcIndexSubstrIfMinlen: <integer>
468 Specify the minimum length for subinitial and subfinal indices. An
469 attribute value must have at least this many characters in order to be
470 processed by the indexing functions. The default is 2.
472 .B olcIndexSubstrAnyLen: <integer>
473 Specify the length used for subany indices. An attribute value must have
474 at least this many characters in order to be processed. Attribute values
475 longer than this length will be processed in segments of this length. The
476 default is 4. The subany index will also be used in subinitial and
477 subfinal index lookups when the filter string is longer than the
478 .I olcIndexSubstrIfMaxlen
481 .B olcIndexSubstrAnyStep: <integer>
482 Specify the steps used in subany index lookups. This value sets the offset
483 for the segments of a filter string that are processed for a subany index
484 lookup. The default is 2. For example, with the default values, a search
485 using this filter "cn=*abcdefgh*" would generate index lookups for
486 "abcd", "cdef", and "efgh".
489 Note: Indexing support depends on the particular backend in use. Also,
490 changing these settings will generally require deleting any indices that
491 depend on these parameters and recreating them with
495 .B olcLocalSSF: <SSF>
496 Specifies the Security Strength Factor (SSF) to be given local LDAP sessions,
497 such as those to the ldapi:// listener. For a description of SSF values,
499 .BR olcSaslSecProps 's
501 option description. The default is 71.
503 .B olcLogFile: <filename>
504 Specify a file for recording debug log messages. By default these messages
505 only go to stderr and are not recorded anywhere else. Specifying a logfile
506 copies messages to both stderr and the logfile.
508 .B olcLogLevel: <integer> [...]
509 Specify the level at which debugging statements and operation
510 statistics should be syslogged (currently logged to the
512 LOG_LOCAL4 facility).
513 They must be considered subsystems rather than increasingly verbose
515 Some messages with higher priority are logged regardless
516 of the configured loglevel as soon as any logging is configured.
517 Log levels are additive, and available levels are:
528 debug packet handling
532 heavy trace debugging (function args)
536 connection management
540 print out packets sent and received
544 search filter processing
548 configuration file processing
552 access control list processing
556 stats log connections/operations/results
560 stats log entries sent
564 print communication with shell backends
576 \"data indexing (unused)
584 only messages that get logged whatever log level is set
587 The desired log level can be input as a single integer that combines
588 the (ORed) desired levels, both in decimal or in hexadecimal notation,
589 as a list of integers (that are ORed internally),
590 or as a list of the names that are shown between brackets, such that
596 olcLogLevel: 0x80 0x1
597 olcLogLevel: acl trace
603 can be used as a shortcut to enable logging at all levels (equivalent to -1).
606 or the equivalent integer representation, causes those messages
607 that are logged regardless of the configured olcLogLevel to be logged.
608 In fact, if no olcLogLevel (or a 0 level) is defined, no logging occurs,
611 level is required to have high priority messages logged.
614 .B olcPasswordCryptSaltFormat: <format>
615 Specify the format of the salt passed to
617 when generating {CRYPT} passwords (see
618 .BR olcPasswordHash )
619 during processing of LDAP Password Modify Extended Operations (RFC 3062).
621 This string needs to be in
623 format and may include one (and only one) %s conversion.
624 This conversion will be substituted with a string of random
625 characters from [A\-Za\-z0\-9./]. For example, "%.2s"
626 provides a two character salt and "$1$%.8s" tells some
627 versions of crypt(3) to use an MD5 algorithm and provides
628 8 random characters of salt. The default is "%s", which
629 provides 31 characters of salt.
631 .B olcPidFile: <filename>
632 The ( absolute ) name of a file that will hold the
634 server's process ID ( see
636 ) if started without the debugging command line option.
638 .B olcPluginLogFile: <filename>
639 The ( absolute ) name of a file that will contain log
646 .B olcReferral: <url>
647 Specify the referral to pass back when
649 cannot find a local database to handle a request.
650 If multiple values are specified, each url is provided.
652 .B olcReverseLookup: TRUE | FALSE
653 Enable/disable client name unverified reverse lookup (default is
655 if compiled with --enable-rlookups).
657 .B olcRootDSE: <file>
658 Specify the name of an LDIF(5) file containing user defined attributes
659 for the root DSE. These attributes are returned in addition to the
660 attributes normally produced by slapd.
662 The root DSE is an entry with information about the server and its
663 capabilities, in operational attributes.
664 It has the empty DN, and can be read with e.g.:
666 ldapsearch -x -b "" -s base "+"
668 See RFC 4512 section 5.1 for details.
670 .B olcSaslHost: <fqdn>
671 Used to specify the fully qualified domain name used for SASL processing.
673 .B olcSaslRealm: <realm>
674 Specify SASL realm. Default is empty.
676 .B olcSaslSecProps: <properties>
677 Used to specify Cyrus SASL security properties.
680 flag (without any other properties) causes the flag properties
681 default, "noanonymous,noplain", to be cleared.
684 flag disables mechanisms susceptible to simple passive attacks.
687 flag disables mechanisms susceptible to active attacks.
690 flag disables mechanisms susceptible to passive dictionary attacks.
693 flag disables mechanisms which support anonymous login.
696 flag require forward secrecy between sessions.
699 require mechanisms which pass client credentials (and allow
700 mechanisms which can pass credentials to do so).
703 property specifies the minimum acceptable
704 .I security strength factor
705 as an integer approximate to effective key length used for
706 encryption. 0 (zero) implies no protection, 1 implies integrity
707 protection only, 56 allows DES or other weak ciphers, 112
708 allows triple DES and other strong ciphers, 128 allows RC4,
709 Blowfish and other modern strong ciphers. The default is 0.
712 property specifies the maximum acceptable
713 .I security strength factor
714 as an integer (see minssf description). The default is INT_MAX.
717 property specifies the maximum security layer receive buffer
718 size allowed. 0 disables security layers. The default is 65536.
720 .B olcServerID: <integer> [<URL>]
721 Specify an integer ID from 0 to 4095 for this server. These IDs are
722 required when using multimaster replication and each master must have a
723 unique ID. If the URL is provided, this directive may be specified
724 multiple times, providing a complete list of participating servers
725 and their IDs. The fully qualified hostname of each server should be
726 used in the supplied URLs. The IDs are used in the "replica id" field
727 of all CSNs generated by the specified server. The default value is zero.
731 olcServerID: 1 ldap://ldap1.example.com
732 olcServerID: 2 ldap://ldap2.example.com
735 .B olcSockbufMaxIncoming: <integer>
736 Specify the maximum incoming LDAP PDU size for anonymous sessions.
737 The default is 262143.
739 .B olcSockbufMaxIncomingAuth: <integer>
740 Specify the maximum incoming LDAP PDU size for authenticated sessions.
741 The default is 4194303.
743 .B olcThreads: <integer>
744 Specify the maximum size of the primary thread pool.
745 The default is 16; the minimum value is 2.
747 .B olcToolThreads: <integer>
748 Specify the maximum number of threads to use in tool mode.
749 This should not be greater than the number of CPUs in the system.
751 .\"ucdata-path is obsolete / ignored...
753 .\".B ucdata-path <path>
754 .\"Specify the path to the directory containing the Unicode character
755 .\"tables. The default path is DATADIR/ucdata.
759 is built with support for Transport Layer Security, there are more options
762 .B olcTLSCipherSuite: <cipher-suite-spec>
763 Permits configuring what ciphers will be accepted and the preference order.
764 <cipher-suite-spec> should be a cipher specification for OpenSSL. Example:
766 olcTLSCipherSuite: HIGH:MEDIUM:+SSLv2
768 To check what ciphers a given spec selects in OpenSSL, use:
771 openssl ciphers -v <cipher-suite-spec>
774 To obtain the list of ciphers in GNUtls use:
780 .B olcTLSCACertificateFile: <filename>
781 Specifies the file that contains certificates for all of the Certificate
786 .B olcTLSCACertificatePath: <path>
787 Specifies the path of a directory that contains Certificate Authority
788 certificates in separate individual files. Usually only one of this
789 or the olcTLSCACertificateFile is defined. If both are specified, both
790 locations will be used. This directive is not supported
793 .B olcTLSCertificateFile: <filename>
794 Specifies the file that contains the
798 .B olcTLSCertificateKeyFile: <filename>
799 Specifies the file that contains the
801 server private key that matches the certificate stored in the
802 .B olcTLSCertificateFile
803 file. If the private key is protected with a password, the password must
804 be manually typed in when slapd starts. Usually the private key is not
805 protected with a password, to allow slapd to start without manual
807 it is of critical importance that the file is protected carefully.
809 .B olcTLSDHParamFile: <filename>
810 This directive specifies the file that contains parameters for Diffie-Hellman
811 ephemeral key exchange. This is required in order to use a DSA certificate on
812 the server. If multiple sets of parameters are present in the file, all of
813 them will be processed. Note that setting this option may also enable
814 Anonymous Diffie-Hellman key exchanges in certain non-default cipher suites.
815 You should append "!ADH" to your cipher suites if you have changed them
816 from the default, otherwise no certificate exchanges or verification will
817 be done. When using GNUtls these parameters are always generated randomly
818 so this directive is ignored.
820 .B olcTLSRandFile: <filename>
821 Specifies the file to obtain random bits from when /dev/[u]random
822 is not available. Generally set to the name of the EGD/PRNGD socket.
823 The environment variable RANDFILE can also be used to specify the filename.
824 This directive is ignored with GNUtls.
826 .B olcTLSVerifyClient: <level>
827 Specifies what checks to perform on client certificates in an
828 incoming TLS session, if any.
831 can be specified as one of the following keywords:
837 will not ask the client for a certificate.
840 The client certificate is requested. If no certificate is provided,
841 the session proceeds normally. If a bad certificate is provided,
842 it will be ignored and the session proceeds normally.
845 The client certificate is requested. If no certificate is provided,
846 the session proceeds normally. If a bad certificate is provided,
847 the session is immediately terminated.
849 .B demand | hard | true
850 These keywords are all equivalent, for compatibility reasons.
851 The client certificate is requested. If no certificate is provided,
852 or a bad certificate is provided, the session is immediately terminated.
854 Note that a valid client certificate is required in order to use the
855 SASL EXTERNAL authentication mechanism with a TLS session. As such,
857 .B olcTLSVerifyClient
858 setting must be chosen to enable SASL EXTERNAL authentication.
861 .B olcTLSCRLCheck: <level>
862 Specifies if the Certificate Revocation List (CRL) of the CA should be
863 used to verify if the client certificates have not been revoked. This
865 .B olcTLSCACertificatePath
866 parameter to be set. This parameter is ignored with GNUtls.
868 can be specified as one of the following keywords:
872 No CRL checks are performed
875 Check the CRL of the peer certificate
878 Check the CRL for a whole certificate chain
881 .B olcTLSCRLFile: <filename>
882 Specifies a file containing a Certificate Revocation List to be used
883 for verifying that certificates have not been revoked. This parameter
884 is only valid when using GNUtls.
885 .SH DYNAMIC MODULE OPTIONS
888 is compiled with --enable-modules then the module-related entries will
889 be available. These entries are named
890 .B cn=module{x},cn=config
892 must have the olcModuleList objectClass. One entry should be created
895 Normally the config engine generates the "{x}" index in the RDN
896 automatically, so it can be omitted when initially loading these entries.
898 .B olcModuleLoad: <filename>
899 Specify the name of a dynamically loadable module to load. The filename
900 may be an absolute path name or a simple filename. Non-absolute names
901 are searched for in the directories specified by the
905 .B olcModulePath: <pathspec>
906 Specify a list of directories to search for loadable modules. Typically
907 the path is colon-separated but this depends on the operating system.
909 Schema definitions are created as entries in the
910 .B cn=schema,cn=config
911 subtree. These entries must have the olcSchemaConfig objectClass.
912 As noted above, the actual
913 .B cn=schema,cn=config
914 entry is predefined and any values specified for it are ignored.
918 .B olcAttributetypes: "(\ <oid>\
920 [DESC\ <description>]\
929 [NO\-USER\-MODIFICATION]\
930 [USAGE\ <attributeUsage>]\ )"
932 Specify an attribute type using the LDAPv3 syntax defined in RFC 4512.
933 The slapd parser extends the RFC 4512 definition by allowing string
934 forms as well as numeric OIDs to be used for the attribute OID and
935 attribute syntax OID.
937 .B olcObjectIdentifier
943 .B olcDitContentRules: "(\ <oid>\
945 [DESC\ <description>]\
952 Specify an DIT Content Rule using the LDAPv3 syntax defined in RFC 4512.
953 The slapd parser extends the RFC 4512 definition by allowing string
954 forms as well as numeric OIDs to be used for the attribute OID and
955 attribute syntax OID.
957 .B olcObjectIdentifier
963 .B olcObjectClasses: "(\ <oid>\
965 [DESC\ <description>]\
968 [{ ABSTRACT | STRUCTURAL | AUXILIARY }]\
969 [MUST\ <oids>] [MAY\ <oids>] )"
971 Specify an objectclass using the LDAPv3 syntax defined in RFC 4512.
972 The slapd parser extends the RFC 4512 definition by allowing string
973 forms as well as numeric OIDs to be used for the object class OID.
977 description.) Object classes are "STRUCTURAL" by default.
980 .B olcObjectIdentifier: <name> "{ <oid> | <name>[:<suffix>] }"
981 Define a string name that equates to the given OID. The string can be used
982 in place of the numeric OID in objectclass and attribute definitions. The
983 name can also be used with a suffix of the form ":xx" in which case the
984 value "oid.xx" will be used.
986 .SH GENERAL BACKEND OPTIONS
987 Options in these entries only apply to the configuration of a single
988 type of backend. All backends may support this class of options.
989 The entry must be named
990 .B olcBackend=<databasetype>,cn=config
991 and must have the olcBackendConfig objectClass.
1009 At present, no backend implements any options of this type.
1011 .SH DATABASE OPTIONS
1012 Database options are set in entries named
1013 .B olcDatabase={x}<databasetype>,cn=config
1014 and must have the olcDatabaseConfig objectClass. Normally the config
1015 engine generates the "{x}" index in the RDN automatically, so it
1016 can be omitted when initially loading these entries.
1018 The special frontend database is always numbered "{-1}" and the config
1019 database is always numbered "{0}".
1021 .SH GLOBAL DATABASE OPTIONS
1022 Options in this section may be set in the special "frontend" database
1023 and inherited in all the other databases. These options may be altered
1024 by further settings in each specific database. The frontend entry must
1026 .B olcDatabase=frontend,cn=config
1027 and must have the olcFrontendConfig objectClass.
1029 .B olcAccess: to <what> "[ by <who> <access> <control> ]+"
1030 Grant access (specified by <access>) to a set of entries and/or
1031 attributes (specified by <what>) by one or more requestors (specified
1033 If no access controls are present, the default policy
1034 allows anyone and everyone to read anything but restricts
1035 updates to rootdn. (e.g., "olcAccess: to * by * read").
1037 .BR slapd.access (5)
1038 and the "OpenLDAP Administrator's Guide" for details.
1040 Access controls set in the frontend are appended to any access
1041 controls set on the specific databases.
1042 The rootdn of a database can always read and write EVERYTHING
1045 Extra special care must be taken with the access controls on the
1046 config database. Unlike other databases, the default policy for the
1047 config database is to only allow access to the rootdn. Regular users
1048 should not have read access, and write access should be granted very
1049 carefully to privileged administrators.
1052 .B olcDefaultSearchBase: <dn>
1053 Specify a default search base to use when client submits a
1054 non-base search request with an empty base DN.
1055 Base scoped search requests with an empty base DN are not affected.
1056 This setting is only allowed in the frontend entry.
1058 .B olcPasswordHash: <hash> [<hash>...]
1059 This option configures one or more hashes to be used in generation of user
1060 passwords stored in the userPassword attribute during processing of
1061 LDAP Password Modify Extended Operations (RFC 3062).
1062 The <hash> must be one of
1076 use the SHA-1 algorithm (FIPS 160-1), the latter with a seed.
1081 use the MD5 algorithm (RFC 1321), the latter with a seed.
1088 indicates that the new password should be
1089 added to userPassword as clear text.
1091 Note that this option does not alter the normal user applications
1092 handling of userPassword during LDAP Add, Modify, or other LDAP operations.
1093 This setting is only allowed in the frontend entry.
1095 .B olcReadOnly: TRUE | FALSE
1096 This option puts the database into "read-only" mode. Any attempts to
1097 modify the database will return an "unwilling to perform" error. By
1098 default, olcReadOnly is FALSE. Note that when this option is set
1099 TRUE on the frontend, it cannot be reset without restarting the
1100 server, since further writes to the config database will be rejected.
1102 .B olcRequires: <conditions>
1103 Specify a set of conditions to require (default none).
1104 The directive may be specified globally and/or per-database;
1105 databases inherit global conditions, so per-database specifications
1108 requires bind operation prior to directory operations.
1110 requires session to be using LDAP version 3.
1112 requires authentication prior to directory operations.
1114 requires SASL authentication prior to directory operations.
1116 requires strong authentication prior to directory operations.
1117 The strong keyword allows protected "simple" authentication
1118 as well as SASL authentication.
1120 may be used to require no conditions (useful to clear out globally
1121 set conditions within a particular database); it must occur first
1122 in the list of conditions.
1124 .B olcRestrict: <oplist>
1125 Specify a list of operations that are restricted.
1126 Restrictions on a specific database override any frontend setting.
1127 Operations can be any of
1132 .BR extended[=<OID>] ,
1136 or the special pseudo-operations
1140 which respectively summarize read and write operations.
1144 .I olcReadOnly: TRUE
1148 keyword allows to indicate the OID of the specific operation
1151 .B olcSchemaDN: <dn>
1152 Specify the distinguished name for the subschema subentry that
1153 controls the entries on this server. The default is "cn=Subschema".
1155 .B olcSecurity: <factors>
1156 Specify a set of security strength factors (separated by white space)
1158 .BR olcSaslSecprops 's
1160 option for a description of security strength factors).
1161 The directive may be specified globally and/or per-database.
1163 specifies the overall security strength factor.
1165 specifies the transport security strength factor.
1167 specifies the TLS security strength factor.
1169 specifies the SASL security strength factor.
1171 specifies the overall security strength factor to require for
1173 .B update_transport=<n>
1174 specifies the transport security strength factor to require for
1177 specifies the TLS security strength factor to require for
1180 specifies the SASL security strength factor to require for
1183 specifies the security strength factor required for
1185 username/password authentication.
1188 factor is measure of security provided by the underlying transport,
1189 e.g. ldapi:// (and eventually IPSEC). It is not normally used.
1191 .B olcSizeLimit: {<integer>|unlimited}
1193 .B olcSizeLimit: size[.{soft|hard|unchecked}]=<integer> [...]
1194 Specify the maximum number of entries to return from a search operation.
1195 The default size limit is 500.
1198 to specify no limits.
1199 The second format allows a fine grain setting of the size limits.
1200 Extra args can be added in the same value or as additional values.
1203 for an explanation of the different flags.
1205 .B olcSortVals <attr> [...]
1206 Specify a list of multi-valued attributes whose values will always
1207 be maintained in sorted order. Using this option will allow Modify,
1208 Compare, and filter evaluations on these attributes to be performed
1209 more efficiently. The resulting sort order depends on the
1210 attributes' syntax and matching rules and may not correspond to
1211 lexical order or any other recognizable order.
1212 This setting is only allowed in the frontend entry.
1214 .B olcTimeLimit: {<integer>|unlimited}
1216 .B olcTimeLimit: time[.{soft|hard}]=<integer> [...]
1217 Specify the maximum number of seconds (in real time)
1219 will spend answering a search request. The default time limit is 3600.
1222 to specify no limits.
1223 The second format allows a fine grain setting of the time limits.
1224 Extra args can be added in the same value or as additional values.
1227 for an explanation of the different flags.
1229 .SH GENERAL DATABASE OPTIONS
1230 Options in this section only apply to the specific database for
1231 which they are defined. They are supported by every
1232 type of backend. All of the Global Database Options may also be
1235 .B olcHidden: TRUE | FALSE
1236 Controls whether the database will be used to answer
1237 queries. A database that is hidden will never be
1238 selected to answer any queries, and any suffix configured
1239 on the database will be ignored in checks for conflicts
1240 with other databases. By default, olcHidden is FALSE.
1242 .B olcLastMod: TRUE | FALSE
1245 will automatically maintain the
1246 modifiersName, modifyTimestamp, creatorsName, and
1247 createTimestamp attributes for entries. It also controls
1248 the entryCSN and entryUUID attributes, which are needed
1249 by the syncrepl provider. By default, olcLastMod is TRUE.
1251 .B olcLimits: <who> <limit> [<limit> [...]]
1252 Specify time and size limits based on who initiated an operation.
1259 anonymous | users | [dn[.<style>]=]<pattern> | group[/oc[/at]]=<pattern>
1265 <style> ::= exact | base | onelevel | subtree | children | regex | anonymous
1270 matches all unauthenticated clients.
1273 matches all authenticated clients;
1276 dn pattern is assumed unless otherwise specified by qualifying
1277 the (optional) key string
1283 (which are synonyms), to require an exact match; with
1285 to require exactly one level of depth match; with
1287 to allow any level of depth match, including the exact match; with
1289 to allow any level of depth match, not including the exact match;
1291 explicitly requires the (default) match based on POSIX (''extended'')
1292 regular expression pattern.
1295 matches unbound operations; the
1298 The same behavior is obtained by using the
1305 with the optional objectClass
1311 sets the limits for any DN listed in the values of the
1317 group objectClass (default
1319 whose DN exactly matches
1322 The currently supported limits are
1327 The syntax for time limits is
1328 .BR time[.{soft|hard}]=<integer> ,
1331 is the number of seconds slapd will spend answering a search request.
1332 If no time limit is explicitly requested by the client, the
1334 limit is used; if the requested time limit exceeds the
1337 .\".I "Administrative limit exceeded"
1338 .\"error is returned.
1339 limit, the value of the limit is used instead.
1342 limit is set to the keyword
1344 the soft limit is used in either case; if it is set to the keyword
1346 no hard limit is enforced.
1347 Explicit requests for time limits smaller or equal to the
1350 If no limit specifier is set, the value is assigned to the
1356 to preserve the original behavior.
1358 The syntax for size limits is
1359 .BR size[.{soft|hard|unchecked}]=<integer> ,
1362 is the maximum number of entries slapd will return answering a search
1364 If no size limit is explicitly requested by the client, the
1366 limit is used; if the requested size limit exceeds the
1369 .\".I "Administrative limit exceeded"
1370 .\"error is returned.
1371 limit, the value of the limit is used instead.
1374 limit is set to the keyword
1376 the soft limit is used in either case; if it is set to the keyword
1378 no hard limit is enforced.
1379 Explicit requests for size limits smaller or equal to the
1384 specifier sets a limit on the number of candidates a search request is allowed
1386 The rationale behind it is that searches for non-properly indexed
1387 attributes may result in large sets of candidates, which must be
1390 to determine whether they match the search filter or not.
1393 limit provides a means to drop such operations before they are even
1395 If the selected candidates exceed the
1397 limit, the search will abort with
1398 .IR "Unwilling to perform" .
1399 If it is set to the keyword
1401 no limit is applied (the default).
1404 the search is not even performed; this can be used to disallow searches
1405 for a specific set of users.
1406 If no limit specifier is set, the value is assigned to the
1412 to preserve the original behavior.
1414 In case of no match, the global limits are used.
1415 The default values are the same as
1424 control is requested, the
1426 size limit is used by default, because the request of a specific page size
1427 is considered an explicit request for a limitation on the number
1428 of entries to be returned.
1429 However, the size limit applies to the total count of entries returned within
1430 the search, and not to a single page.
1431 Additional size limits may be enforced; the syntax is
1432 .BR size.pr={<integer>|noEstimate|unlimited} ,
1435 is the max page size if no explicit limit is set; the keyword
1437 inhibits the server from returning an estimate of the total number
1438 of entries that might be returned
1439 (note: the current implementation does not return any estimate).
1442 indicates that no limit is applied to the pagedResults control page size.
1444 .B size.prtotal={<integer>|unlimited|disabled}
1445 allows to set a limit on the total number of entries that a pagedResults
1446 control allows to return.
1447 By default it is set to the
1452 is the max number of entries that the whole search with pagedResults control
1456 to allow unlimited number of entries to be returned, e.g. to allow
1457 the use of the pagedResults control as a means to circumvent size
1458 limitations on regular searches; the keyword
1460 disables the control, i.e. no paged results can be returned.
1461 Note that the total number of entries returned when the pagedResults control
1462 is requested cannot exceed the
1464 size limit of regular searches unless extended by the
1469 .B olcMaxDerefDepth: <depth>
1470 Specifies the maximum number of aliases to dereference when trying to
1471 resolve an entry, used to avoid infinite alias loops. The default is 15.
1473 .B olcMirrorMode: TRUE | FALSE
1474 This option puts a replica database into "mirror" mode. Update
1475 operations will be accepted from any user, not just the updatedn. The
1476 database must already be configured as syncrepl consumer
1477 before this keyword may be set. This mode also requires a
1479 (see above) to be configured.
1480 By default, this setting is FALSE.
1482 .B olcPlugin: <plugin_type> <lib_path> <init_function> [<arguments>]
1483 Configure a SLAPI plugin. See the
1484 .BR slapd.plugin (5)
1485 manpage for more details.
1488 Specify the distinguished name that is not subject to access control
1489 or administrative limit restrictions for operations on this database.
1490 This DN may or may not be associated with an entry. An empty root
1491 DN (the default) specifies no root access is to be granted. It is
1492 recommended that the rootdn only be specified when needed (such as
1493 when initially populating a database). If the rootdn is within
1494 a namingContext (suffix) of the database, a simple bind password
1495 may also be provided using the
1497 directive. Note that the rootdn is always needed when using syncrepl.
1499 .B olcRootPW: <password>
1500 Specify a password (or hash of the password) for the rootdn. The
1501 password can only be set if the rootdn is within the namingContext
1502 (suffix) of the database.
1503 This option accepts all RFC 2307 userPassword formats known to
1506 description) as well as cleartext.
1508 may be used to generate a hash of a password. Cleartext
1509 and \fB{CRYPT}\fP passwords are not recommended. If empty
1510 (the default), authentication of the root DN is by other means
1511 (e.g. SASL). Use of SASL is encouraged.
1513 .B olcSubordinate: [TRUE | FALSE | advertise]
1514 Specify that the current backend database is a subordinate of another
1515 backend database. A subordinate database may have only one suffix. This
1516 option may be used to glue multiple databases into a single namingContext.
1517 If the suffix of the current database is within the namingContext of a
1518 superior database, searches against the superior database will be
1519 propagated to the subordinate as well. All of the databases
1520 associated with a single namingContext should have identical rootdns.
1521 Behavior of other LDAP operations is unaffected by this setting. In
1522 particular, it is not possible to use moddn to move an entry from
1523 one subordinate to another subordinate within the namingContext.
1525 If the optional \fBadvertise\fP flag is supplied, the naming context of
1526 this database is advertised in the root DSE. The default is to hide this
1527 database context, so that only the superior context is visible.
1534 are used on the superior database, any glued subordinates that support
1535 these tools are opened as well.
1537 Databases that are glued together should usually be configured with the
1538 same indices (assuming they support indexing), even for attributes that
1539 only exist in some of these databases. In general, all of the glued
1540 databases should be configured as similarly as possible, since the intent
1541 is to provide the appearance of a single directory.
1543 Note that the subordinate functionality is implemented internally
1544 by the \fIglue\fP overlay and as such its behavior will interact with other
1545 overlays in use. By default, the glue overlay is automatically configured as
1546 the last overlay on the superior database. Its position on the database
1547 can be explicitly configured by setting an \fBoverlay glue\fP directive
1548 at the desired position. This explicit configuration is necessary e.g.
1549 when using the \fIsyncprov\fP overlay, which needs to follow \fIglue\fP
1550 in order to work over all of the glued databases. E.g.
1553 dn: olcDatabase={1}bdb,cn=config
1554 olcSuffix: dc=example,dc=com
1557 dn: olcOverlay={0}glue,olcDatabase={1}bdb,cn=config
1560 dn: olcOverlay={1}syncprov,olcDatabase={1}bdb,cn=config
1564 See the Overlays section below for more details.
1566 .B olcSuffix: <dn suffix>
1567 Specify the DN suffix of queries that will be passed to this
1568 backend database. Multiple suffix lines can be given and at least one is
1569 required for each database definition.
1570 If the suffix of one database is "inside" that of another, the database
1571 with the inner suffix must come first in the configuration file.
1574 .B olcSyncrepl: rid=<replica ID>
1575 .B provider=ldap[s]://<hostname>[:port]
1576 .B searchbase=<base DN>
1577 .B [type=refreshOnly|refreshAndPersist]
1578 .B [interval=dd:hh:mm:ss]
1579 .B [retry=[<retry interval> <# of retries>]+]
1580 .B [filter=<filter str>]
1581 .B [scope=sub|one|base|subord]
1582 .B [attrs=<attr list>]
1583 .B [exattrs=<attr list>]
1585 .B [sizelimit=<limit>]
1586 .B [timelimit=<limit>]
1587 .B [schemachecking=on|off]
1588 .B [bindmethod=simple|sasl]
1590 .B [saslmech=<mech>]
1591 .B [authcid=<identity>]
1592 .B [authzid=<identity>]
1593 .B [credentials=<passwd>]
1595 .B [secprops=<properties>]
1596 .B [starttls=yes|critical]
1597 .B [tls_cert=<file>]
1599 .B [tls_cacert=<file>]
1600 .B [tls_cacertdir=<path>]
1601 .B [tls_reqcert=never|allow|try|demand]
1602 .B [tls_ciphersuite=<ciphers>]
1603 .B [tls_crlcheck=none|peer|all]
1604 .B [logbase=<base DN>]
1605 .B [logfilter=<filter str>]
1606 .B [syncdata=default|accesslog|changelog]
1608 Specify the current database as a replica which is kept up-to-date with the
1609 master content by establishing the current
1611 as a replication consumer site running a
1614 The replica content is kept synchronized to the master content using
1615 the LDAP Content Synchronization protocol. Refer to the
1616 "OpenLDAP Administrator's Guide" for detailed information on
1617 setting up a replicated
1619 directory service using the
1624 identifies the current
1626 directive within the replication consumer site.
1627 It is a non-negative integer having no more than three digits.
1630 specifies the replication provider site containing the master content
1631 as an LDAP URI. If <port> is not given, the standard LDAP port number
1632 (389 or 636) is used.
1636 replica is defined using a search
1637 specification as its result set. The consumer
1639 will send search requests to the provider
1641 according to the search specification. The search specification includes
1642 .B searchbase, scope, filter, attrs, attrsonly, sizelimit,
1645 parameters as in the normal search specification. The
1647 option may also be used to specify attributes that should be omitted
1648 from incoming entries.
1649 The \fBscope\fP defaults to \fBsub\fP, the \fBfilter\fP defaults to
1650 \fB(objectclass=*)\fP, and there is no default \fBsearchbase\fP. The
1651 \fBattrs\fP list defaults to \fB"*,+"\fP to return all user and operational
1652 attributes, and \fBattrsonly\fP and \fBexattrs\fP are unset by default.
1653 The \fBsizelimit\fP and \fBtimelimit\fP only
1654 accept "unlimited" and positive integers, and both default to "unlimited".
1655 Note, however, that any provider-side limits for the replication identity
1656 will be enforced by the provider regardless of the limits requested
1657 by the LDAP Content Synchronization operation, much like for any other
1660 The LDAP Content Synchronization protocol has two operation types.
1663 operation, the next synchronization search operation
1664 is periodically rescheduled at an interval time (specified by
1666 parameter; 1 day by default)
1667 after each synchronization operation finishes.
1669 .B refreshAndPersist
1670 operation, a synchronization search remains persistent in the provider slapd.
1671 Further updates to the master replica will generate
1672 .B searchResultEntry
1673 to the consumer slapd as the search responses to the persistent
1674 synchronization search.
1676 If an error occurs during replication, the consumer will attempt to
1677 reconnect according to the
1679 parameter which is a list of the <retry interval> and <# of retries> pairs.
1680 For example, retry="60 10 300 3" lets the consumer retry every 60 seconds
1681 for the first 10 times and then retry every 300 seconds for the next 3
1682 times before stop retrying. The `+' in <# of retries> means indefinite
1683 number of retries until success.
1685 The schema checking can be enforced at the LDAP Sync
1686 consumer site by turning on the
1688 parameter. The default is off.
1694 requires the options
1698 and should only be used when adequate security services
1699 (e.g. TLS or IPSEC) are in place.
1706 Depending on the mechanism, an authentication identity and/or
1707 credentials can be specified using
1713 parameter may be used to specify an authorization identity.
1714 Specific security properties (as with the
1716 keyword above) for a SASL bind can be set with the
1718 option. A non default SASL realm can be set with the
1721 The provider, other than allow authentication of the syncrepl identity,
1722 should grant that identity appropriate access privileges to the data
1723 that is being replicated (\fBaccess\fP directive), and appropriate time
1724 and size limits (\fBlimits\fP directive).
1729 parameter specifies use of the StartTLS extended operation
1730 to establish a TLS session before Binding to the provider. If the
1732 argument is supplied, the session will be aborted if the StartTLS request
1733 fails. Otherwise the syncrepl session continues without TLS. The
1734 tls_reqcert setting defaults to "demand" and the other TLS settings
1735 default to the same as the main slapd TLS settings.
1737 Rather than replicating whole entries, the consumer can query logs of
1738 data modifications. This mode of operation is referred to as \fIdelta
1739 syncrepl\fP. In addition to the above parameters, the
1743 parameters must be set appropriately for the log that will be used. The
1745 parameter must be set to either "accesslog" if the log conforms to the
1746 .BR slapo-accesslog (5)
1747 log format, or "changelog" if the log conforms
1748 to the obsolete \fIchangelog\fP format. If the
1750 parameter is omitted or set to "default" then the log parameters are
1754 .B olcUpdateDN: <dn>
1755 This option is only applicable in a slave
1757 It specifies the DN permitted to update (subject to access controls)
1758 the replica. It is only needed in certain push-mode
1759 replication scenarios. Generally, this DN
1765 .B olcUpdateRef: <url>
1766 Specify the referral to pass back when
1768 is asked to modify a replicated local database.
1769 If multiple values are specified, each url is provided.
1771 .SH DATABASE-SPECIFIC OPTIONS
1772 Each database may allow specific configuration options; they are
1773 documented separately in the backends' manual pages. See the
1774 .BR slapd.backends (5)
1775 manual page for an overview of available backends.
1777 An overlay is a piece of
1778 code that intercepts database operations in order to extend or change
1779 them. Overlays are pushed onto
1780 a stack over the database, and so they will execute in the reverse
1781 of the order in which they were configured and the database itself
1782 will receive control last of all.
1784 Overlays must be configured as child entries of a specific database. The
1785 entry's RDN must be of the form
1786 .B olcOverlay={x}<overlaytype>
1787 and the entry must have the olcOverlayConfig objectClass. Normally the
1788 config engine generates the "{x}" index in the RDN automatically, so
1789 it can be omitted when initially loading these entries.
1792 .BR slapd.overlays (5)
1793 manual page for an overview of available overlays.
1796 Here is a short example of a configuration in LDIF suitable for use with
1803 objectClass: olcGlobal
1805 olcPidFile: LOCALSTATEDIR/run/slapd.pid
1806 olcAttributeOptions: x-hidden lang-
1808 dn: cn=schema,cn=config
1809 objectClass: olcSchemaConfig
1812 include: SYSCONFDIR/schema/core.ldif
1814 dn: olcDatabase=frontend,cn=config
1815 objectClass: olcDatabaseConfig
1816 objectClass: olcFrontendConfig
1817 olcDatabase: frontend
1818 # Subtypes of "name" (e.g. "cn" and "ou") with the
1819 # option ";x-hidden" can be searched for/compared,
1820 # but are not shown. See \fBslapd.access\fP(5).
1821 olcAccess: to attrs=name;x-hidden by * =cs
1822 # Protect passwords. See \fBslapd.access\fP(5).
1823 olcAccess: to attrs=userPassword by * auth
1824 # Read access to other attributes and entries.
1825 olcAccess: to * by * read
1827 # set a rootpw for the config database so we can bind.
1828 # deny access to everyone else.
1829 dn: olcDatabase=config,cn=config
1830 objectClass: olcDatabaseConfig
1832 olcRootPW: {SSHA}XKYnrjvGT3wZFQrDD5040US592LxsdLy
1833 olcAccess: to * by * none
1835 dn: olcDatabase=bdb,cn=config
1836 objectClass: olcDatabaseConfig
1837 objectClass: olcBdbConfig
1839 olcSuffix: "dc=our-domain,dc=com"
1840 # The database directory MUST exist prior to
1841 # running slapd AND should only be accessible
1842 # by the slapd/tools. Mode 0700 recommended.
1843 olcDbDirectory: LOCALSTATEDIR/openldap-data
1844 # Indices to maintain
1845 olcDbIndex: objectClass eq
1846 olcDbIndex: cn,sn,mail pres,eq,approx,sub
1848 # We serve small clients that do not handle referrals,
1849 # so handle remote lookups on their behalf.
1850 dn: olcDatabase=ldap,cn=config
1851 objectClass: olcDatabaseConfig
1852 objectClass: olcLdapConfig
1855 olcDbUri: ldap://ldap.some-server.com/
1859 Assuming the above data was saved in a file named "config.ldif" and the
1860 ETCDIR/slapd.d directory has been created, this command will initialize
1864 slapadd -F ETCDIR/slapd.d -n 0 -l config.ldif
1869 "OpenLDAP Administrator's Guide" contains a longer annotated
1870 example of a slapd configuration.
1872 Alternatively, an existing slapd.conf file can be converted to the new
1873 format using slapd or any of the slap tools:
1876 slaptest -f ETCDIR/slapd.conf -F ETCDIR/slapd.d
1883 default slapd configuration file
1886 default slapd configuration directory
1890 .BR slapd.access (5),
1891 .BR slapd.backends (5),
1893 .BR slapd.overlays (5),
1894 .BR slapd.plugin (5),
1895 .BR slapd.replog (5),
1906 "OpenLDAP Administrator's Guide" (http://www.OpenLDAP.org/doc/admin/)
1907 .SH ACKNOWLEDGEMENTS
projects / openldap / blob