1 .TH SLAPD-CONFIG 5 "RELEASEDATE" "OpenLDAP LDVERSION"
2 .\" Copyright 1998-2013 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 (program name and options).
149 .B olcAttributeOptions: <option-name>...
150 Define tagging attribute options or option tag/range prefixes.
151 Options must not end with `\-', prefixes must end with `\-'.
152 The `lang\-' prefix is predefined.
154 .B olcAttributeOptions
155 directive, `lang\-' will no longer be defined and you must specify it
156 explicitly if you want it defined.
158 An attribute description with a tagging option is a subtype of that
159 attribute description without the option.
160 Except for that, options defined this way have no special semantics.
161 Prefixes defined this way work like the `lang\-' options:
162 They define a prefix for tagging options starting with the prefix.
163 That is, if you define the prefix `x\-foo\-', you can use the option
165 Furthermore, in a search or compare, a prefix or range name (with
166 a trailing `\-') matches all options starting with that name, as well
167 as the option with the range name sans the trailing `\-'.
168 That is, `x\-foo\-bar\-' matches `x\-foo\-bar' and `x\-foo\-bar\-baz'.
170 RFC 4520 reserves options beginning with `x\-' for private experiments.
171 Other options should be registered with IANA, see RFC 4520 section 3.5.
172 OpenLDAP also has the `binary' option built in, but this is a transfer
173 option, not a tagging option.
175 .B olcAuthIDRewrite: <rewrite\-rule>
176 Used by the authentication framework to convert simple user names
177 to an LDAP DN used for authorization purposes.
178 Its purpose is analogous to that of
183 is a set of rules analogous to those described in
185 for data rewriting (after stripping the \fIrwm\-\fP prefix).
189 should not be intermixed.
191 .B olcAuthzPolicy: <policy>
192 Used to specify which rules to use for Proxy Authorization. Proxy
193 authorization allows a client to authenticate to the server using one
194 user's credentials, but specify a different identity to use for authorization
195 and access control purposes. It essentially allows user A to login as user
196 B, using user A's password.
199 flag disables proxy authorization. This is the default setting.
202 flag will use rules in the
204 attribute of the authorization DN.
207 flag will use rules in the
209 attribute of the authentication DN.
212 flag, an alias for the deprecated value of
214 will allow any of the above, whatever succeeds first (checked in
220 flag requires both authorizations to succeed.
223 The rules are mechanisms to specify which identities are allowed
224 to perform proxy authorization.
227 attribute in an entry specifies which other users
228 are allowed to proxy login to this entry. The
231 an entry specifies which other users this user can authorize as. Use of
234 abused if users are allowed to write arbitrary values to this attribute.
237 attribute must be protected with ACLs such that
238 only privileged users can modify it.
245 or a set of identities; it can take five forms:
248 .B ldap:///<base>??[<scope>]?<filter>
251 .B dn[.<dnstyle>]:<pattern>
254 .B u[<mech>[<realm>]]:<pattern>
257 .B group[/objectClass[/attributeType]]:<pattern>
264 .B <dnstyle>:={exact|onelevel|children|subtree|regex}
267 The first form is a valid LDAP
275 portions must be absent, so that the search occurs locally on either
281 with the optional style modifiers
287 for exact, onelevel, children and subtree matches, which cause
289 to be normalized according to the DN normalization rules, or the special
291 style, which causes the
293 to be treated as a POSIX (''extended'') regular expression, as
300 means any non-anonymous DN.
301 The third form is a SASL
303 with the optional fields
307 that allow to specify a SASL
309 and eventually a SASL
311 for those mechanisms that support one.
312 The need to allow the specification of a mechanism is still debated,
313 and users are strongly discouraged to rely on this possibility.
314 The fourth form is a group specification, consisting of the keyword
316 optionally followed by the specification of the group
322 is searched with base scope, and in case of match, the values of the
325 are searched for the asserted DN.
326 For backwards compatibility, if no identity type is provided, i.e. only
330 is assumed; as a consequence,
332 is subjected to DN normalization.
333 Since the interpretation of
337 can impact security, users are strongly encouraged
338 to explicitly set the type of identity specification that is being used.
339 A subset of these rules can be used as third arg in the
341 statement (see below); significantly, the
348 .B olcAuthzRegexp: <match> <replace>
349 Used by the authentication framework to convert simple user names,
350 such as provided by SASL subsystem, to an LDAP DN used for
351 authorization purposes. Note that the resultant DN need not refer
352 to an existing entry to be considered valid. When an authorization
353 request is received from the SASL subsystem, the SASL
358 are taken, when available, and combined into a name of the form
362 .B UID=<username>[[,CN=<realm>],CN=<mechanism>],CN=auth
365 This name is then compared against the
367 POSIX (''extended'') regular expression, and if the match is successful,
368 the name is replaced with the
370 string. If there are wildcard strings in the
372 regular expression that are enclosed in parenthesis, e.g.
378 then the portion of the name that matched the wildcard will be stored
379 in the numbered placeholder variable $1. If there are other wildcard strings
380 in parenthesis, the matching strings will be in $2, $3, etc. up to $9. The
381 placeholders can then be used in the
386 .B UID=$1,OU=Accounts,DC=example,DC=com
389 The replaced name can be either a DN, i.e. a string prefixed by "dn:",
391 If the latter, the server will use the URI to search its own database(s)
392 and, if the search returns exactly one entry, the name is
393 replaced by the DN of that entry. The LDAP URI must have no
394 hostport, attrs, or extensions components, but the filter is mandatory,
398 .B ldap:///OU=Accounts,DC=example,DC=com??one?(UID=$1)
401 The protocol portion of the URI must be strictly
403 Note that this search is subject to access controls. Specifically,
404 the authentication identity must have "auth" access in the subject.
408 values can be specified to allow for multiple matching
409 and replacement patterns. The matching patterns are checked in the order they
410 appear in the attribute, stopping at the first successful match.
413 .\"Because the plus sign + is a character recognized by the regular expression engine,
414 .\"and it will appear in names that include a REALM, be careful to escape the
415 .\"plus sign with a backslash \\+ to remove the character's special meaning.
418 .B olcConcurrency: <integer>
419 Specify a desired level of concurrency. Provided to the underlying
420 thread system as a hint. The default is not to provide any hint. This setting
421 is only meaningful on some platforms where there is not a one to one
422 correspondence between user threads and kernel threads.
424 .B olcConnMaxPending: <integer>
425 Specify the maximum number of pending requests for an anonymous session.
426 If requests are submitted faster than the server can process them, they
427 will be queued up to this limit. If the limit is exceeded, the session
428 is closed. The default is 100.
430 .B olcConnMaxPendingAuth: <integer>
431 Specify the maximum number of pending requests for an authenticated session.
434 .B olcDisallows: <features>
435 Specify a set of features to disallow (default none).
437 disables acceptance of anonymous bind requests. Note that this setting
438 does not prohibit anonymous directory access (See "require authc").
440 disables simple (bind) authentication.
442 disables forcing session to anonymous status (see also
444 upon StartTLS operation receipt.
446 disallows the StartTLS operation if authenticated (see also
449 .B olcGentleHUP: { TRUE | FALSE }
450 A SIGHUP signal will only cause a 'gentle' shutdown-attempt:
452 will stop listening for new connections, but will not close the
453 connections to the current clients. Future write operations return
454 unwilling-to-perform, though. Slapd terminates when all clients
455 have closed their connections (if they ever do), or - as before -
456 if it receives a SIGTERM signal. This can be useful if you wish to
457 terminate the server and start a new
460 .B with another database,
461 without disrupting the currently active clients.
462 The default is FALSE. You may wish to use
464 along with this option.
466 .B olcIdleTimeout: <integer>
467 Specify the number of seconds to wait before forcibly closing
468 an idle client connection. A setting of 0 disables this
469 feature. The default is 0. You may also want to set the
473 .B olcIndexIntLen: <integer>
474 Specify the key length for ordered integer indices. The most significant
475 bytes of the binary integer will be used for index keys. The default
476 value is 4, which provides exact indexing for 31 bit values.
477 A floating point representation is used to index too large values.
479 .B olcIndexSubstrIfMaxlen: <integer>
480 Specify the maximum length for subinitial and subfinal indices. Only
481 this many characters of an attribute value will be processed by the
482 indexing functions; any excess characters are ignored. The default is 4.
484 .B olcIndexSubstrIfMinlen: <integer>
485 Specify the minimum length for subinitial and subfinal indices. An
486 attribute value must have at least this many characters in order to be
487 processed by the indexing functions. The default is 2.
489 .B olcIndexSubstrAnyLen: <integer>
490 Specify the length used for subany indices. An attribute value must have
491 at least this many characters in order to be processed. Attribute values
492 longer than this length will be processed in segments of this length. The
493 default is 4. The subany index will also be used in subinitial and
494 subfinal index lookups when the filter string is longer than the
495 .I olcIndexSubstrIfMaxlen
498 .B olcIndexSubstrAnyStep: <integer>
499 Specify the steps used in subany index lookups. This value sets the offset
500 for the segments of a filter string that are processed for a subany index
501 lookup. The default is 2. For example, with the default values, a search
502 using this filter "cn=*abcdefgh*" would generate index lookups for
503 "abcd", "cdef", and "efgh".
506 Note: Indexing support depends on the particular backend in use. Also,
507 changing these settings will generally require deleting any indices that
508 depend on these parameters and recreating them with
512 .B olcListenerThreads: <integer>
513 Specify the number of threads to use for the connection manager.
514 The default is 1 and this is typically adequate for up to 16 CPU cores.
515 The value should be set to a power of 2.
517 .B olcLocalSSF: <SSF>
518 Specifies the Security Strength Factor (SSF) to be given local LDAP sessions,
519 such as those to the ldapi:// listener. For a description of SSF values,
521 .BR olcSaslSecProps 's
523 option description. The default is 71.
525 .B olcLogFile: <filename>
526 Specify a file for recording debug log messages. By default these messages
527 only go to stderr and are not recorded anywhere else. Specifying a logfile
528 copies messages to both stderr and the logfile.
530 .B olcLogLevel: <integer> [...]
531 Specify the level at which debugging statements and operation
532 statistics should be syslogged (currently logged to the
534 LOG_LOCAL4 facility).
535 They must be considered subsystems rather than increasingly verbose
537 Some messages with higher priority are logged regardless
538 of the configured loglevel as soon as any logging is configured.
539 Log levels are additive, and available levels are:
550 debug packet handling
554 heavy trace debugging (function args)
558 connection management
562 print out packets sent and received
566 search filter processing
570 configuration file processing
574 access control list processing
578 stats log connections/operations/results
582 stats log entries sent
586 print communication with shell backends
598 \"data indexing (unused)
606 only messages that get logged whatever log level is set
609 The desired log level can be input as a single integer that combines
610 the (ORed) desired levels, both in decimal or in hexadecimal notation,
611 as a list of integers (that are ORed internally),
612 or as a list of the names that are shown between brackets, such that
618 olcLogLevel: 0x80 0x1
619 olcLogLevel: acl trace
625 can be used as a shortcut to enable logging at all levels (equivalent to \-1).
628 or the equivalent integer representation, causes those messages
629 that are logged regardless of the configured olcLogLevel to be logged.
630 In fact, if no olcLogLevel (or a 0 level) is defined, no logging occurs,
633 level is required to have high priority messages logged.
636 .B olcPasswordCryptSaltFormat: <format>
637 Specify the format of the salt passed to
639 when generating {CRYPT} passwords (see
640 .BR olcPasswordHash )
641 during processing of LDAP Password Modify Extended Operations (RFC 3062).
643 This string needs to be in
645 format and may include one (and only one) %s conversion.
646 This conversion will be substituted with a string of random
647 characters from [A\-Za\-z0\-9./]. For example, "%.2s"
648 provides a two character salt and "$1$%.8s" tells some
649 versions of crypt(3) to use an MD5 algorithm and provides
650 8 random characters of salt. The default is "%s", which
651 provides 31 characters of salt.
653 .B olcPidFile: <filename>
654 The (absolute) name of a file that will hold the
656 server's process ID (see
659 .B olcPluginLogFile: <filename>
660 The ( absolute ) name of a file that will contain log
667 .B olcReferral: <url>
668 Specify the referral to pass back when
670 cannot find a local database to handle a request.
671 If multiple values are specified, each url is provided.
673 .B olcReverseLookup: TRUE | FALSE
674 Enable/disable client name unverified reverse lookup (default is
676 if compiled with \-\-enable\-rlookups).
678 .B olcRootDSE: <file>
679 Specify the name of an LDIF(5) file containing user defined attributes
680 for the root DSE. These attributes are returned in addition to the
681 attributes normally produced by slapd.
683 The root DSE is an entry with information about the server and its
684 capabilities, in operational attributes.
685 It has the empty DN, and can be read with e.g.:
687 ldapsearch \-x \-b "" \-s base "+"
689 See RFC 4512 section 5.1 for details.
691 .B olcSaslAuxprops: <plugin> [...]
692 Specify which auxprop plugins to use for authentication lookups. The
693 default is empty, which just uses slapd's internal support. Usually
694 no other auxprop plugins are needed.
696 .B olcSaslHost: <fqdn>
697 Used to specify the fully qualified domain name used for SASL processing.
699 .B olcSaslRealm: <realm>
700 Specify SASL realm. Default is empty.
702 .B olcSaslSecProps: <properties>
703 Used to specify Cyrus SASL security properties.
706 flag (without any other properties) causes the flag properties
707 default, "noanonymous,noplain", to be cleared.
710 flag disables mechanisms susceptible to simple passive attacks.
713 flag disables mechanisms susceptible to active attacks.
716 flag disables mechanisms susceptible to passive dictionary attacks.
719 flag disables mechanisms which support anonymous login.
722 flag require forward secrecy between sessions.
725 require mechanisms which pass client credentials (and allow
726 mechanisms which can pass credentials to do so).
729 property specifies the minimum acceptable
730 .I security strength factor
731 as an integer approximate to effective key length used for
732 encryption. 0 (zero) implies no protection, 1 implies integrity
733 protection only, 56 allows DES or other weak ciphers, 112
734 allows triple DES and other strong ciphers, 128 allows RC4,
735 Blowfish and other modern strong ciphers. The default is 0.
738 property specifies the maximum acceptable
739 .I security strength factor
740 as an integer (see minssf description). The default is INT_MAX.
743 property specifies the maximum security layer receive buffer
744 size allowed. 0 disables security layers. The default is 65536.
746 .B olcServerID: <integer> [<URL>]
747 Specify an integer ID from 0 to 4095 for this server (limited
748 to 3 hexadecimal digits). The ID may also be specified as a
749 hexadecimal ID by prefixing the value with "0x".
751 required when using multimaster replication and each master must have a
752 unique ID. Note that this requirement also applies to separate masters
753 contributing to a glued set of databases.
754 If the URL is provided, this directive may be specified
755 multiple times, providing a complete list of participating servers
756 and their IDs. The fully qualified hostname of each server should be
757 used in the supplied URLs. The IDs are used in the "replica id" field
758 of all CSNs generated by the specified server. The default value is zero.
762 olcServerID: 1 ldap://ldap1.example.com
763 olcServerID: 2 ldap://ldap2.example.com
766 .B olcSockbufMaxIncoming: <integer>
767 Specify the maximum incoming LDAP PDU size for anonymous sessions.
768 The default is 262143.
770 .B olcSockbufMaxIncomingAuth: <integer>
771 Specify the maximum incoming LDAP PDU size for authenticated sessions.
772 The default is 4194303.
774 .B olcTCPBuffer [listener=<URL>] [{read|write}=]<size>
775 Specify the size of the TCP buffer.
776 A global value for both read and write TCP buffers related to any listener
777 is defined, unless the listener is explicitly specified,
778 or either the read or write qualifiers are used.
782 Note that some OS-es implement automatic TCP buffer tuning.
784 .B olcThreads: <integer>
785 Specify the maximum size of the primary thread pool.
786 The default is 16; the minimum value is 2.
788 .B olcToolThreads: <integer>
789 Specify the maximum number of threads to use in tool mode.
790 This should not be greater than the number of CPUs in the system.
793 .B olcWriteTimeout: <integer>
794 Specify the number of seconds to wait before forcibly closing
795 a connection with an outstanding write. This allows recovery from
796 various network hang conditions. A setting of 0 disables this
797 feature. The default is 0.
801 is built with support for Transport Layer Security, there are more options
804 .B olcTLSCipherSuite: <cipher-suite-spec>
805 Permits configuring what ciphers will be accepted and the preference order.
806 <cipher-suite-spec> should be a cipher specification for
807 the TLS library in use (OpenSSL, GnuTLS, or Mozilla NSS).
813 olcTLSCipherSuite: HIGH:MEDIUM:+SSLv2
816 TLSCiphersuite SECURE256:!AES-128-CBC
819 To check what ciphers a given spec selects in OpenSSL, use:
822 openssl ciphers \-v <cipher-suite-spec>
825 With GnuTLS the available specs can be found in the manual page of
827 (see the description of the
831 In older versions of GnuTLS, where gnutls\-cli does not support the option
832 \-\-priority, you can obtain the \(em more limited \(em list of ciphers by calling:
838 When using Mozilla NSS, the OpenSSL cipher suite specifications are used and
839 translated into the format used internally by Mozilla NSS. There isn't an easy
840 way to list the cipher suites from the command line. The authoritative list
841 is in the source code for Mozilla NSS in the file sslinfo.c in the structure
843 static const SSLCipherSuiteInfo suiteInfo[]
847 .B olcTLSCACertificateFile: <filename>
848 Specifies the file that contains certificates for all of the Certificate
853 .B olcTLSCACertificatePath: <path>
854 Specifies the path of a directory that contains Certificate Authority
855 certificates in separate individual files. Usually only one of this
856 or the olcTLSCACertificateFile is defined. If both are specified, both
857 locations will be used. This directive is not supported
860 When using Mozilla NSS, <path> may contain a Mozilla NSS cert/key
861 database. If <path> contains a Mozilla NSS cert/key database and
862 CA cert files, OpenLDAP will use the cert/key database and will
863 ignore the CA cert files.
865 .B olcTLSCertificateFile: <filename>
866 Specifies the file that contains the
870 When using Mozilla NSS, if using a cert/key database (specified with
871 olcTLSCACertificatePath), olcTLSCertificateFile specifies
872 the name of the certificate to use:
874 olcTLSCertificateFile: Server-Cert
876 If using a token other than the internal built in token, specify the
877 token name first, followed by a colon:
879 olcTLSCertificateFile: my hardware device:Server-Cert
881 Use certutil -L to list the certificates by name:
883 certutil -d /path/to/certdbdir -L
886 .B olcTLSCertificateKeyFile: <filename>
887 Specifies the file that contains the
889 server private key that matches the certificate stored in the
890 .B olcTLSCertificateFile
891 file. If the private key is protected with a password, the password must
892 be manually typed in when slapd starts. Usually the private key is not
893 protected with a password, to allow slapd to start without manual
895 it is of critical importance that the file is protected carefully.
897 When using Mozilla NSS, olcTLSCertificateKeyFile specifies the name of
898 a file that contains the password for the key for the certificate specified with
899 olcTLSCertificateFile. The modutil command can be used to turn off password
900 protection for the cert/key database. For example, if olcTLSCACertificatePath
901 specifes /etc/openldap/certdb as the location of the cert/key database, use
902 modutil to change the password to the empty string:
904 modutil -dbdir /etc/openldap/certdb -changepw 'NSS Certificate DB'
906 You must have the old password, if any. Ignore the WARNING about the running
907 browser. Press 'Enter' for the new password.
910 .B olcTLSDHParamFile: <filename>
911 This directive specifies the file that contains parameters for Diffie-Hellman
912 ephemeral key exchange. This is required in order to use a DSA certificate on
913 the server. If multiple sets of parameters are present in the file, all of
914 them will be processed. Note that setting this option may also enable
915 Anonymous Diffie-Hellman key exchanges in certain non-default cipher suites.
916 You should append "!ADH" to your cipher suites if you have changed them
917 from the default, otherwise no certificate exchanges or verification will
918 be done. When using GnuTLS or Mozilla NSS these parameters are always generated randomly
919 so this directive is ignored.
921 .B olcTLSRandFile: <filename>
922 Specifies the file to obtain random bits from when /dev/[u]random
923 is not available. Generally set to the name of the EGD/PRNGD socket.
924 The environment variable RANDFILE can also be used to specify the filename.
925 This directive is ignored with GnuTLS and Mozilla NSS.
927 .B olcTLSVerifyClient: <level>
928 Specifies what checks to perform on client certificates in an
929 incoming TLS session, if any.
932 can be specified as one of the following keywords:
938 will not ask the client for a certificate.
941 The client certificate is requested. If no certificate is provided,
942 the session proceeds normally. If a bad certificate is provided,
943 it will be ignored and the session proceeds normally.
946 The client certificate is requested. If no certificate is provided,
947 the session proceeds normally. If a bad certificate is provided,
948 the session is immediately terminated.
950 .B demand | hard | true
951 These keywords are all equivalent, for compatibility reasons.
952 The client certificate is requested. If no certificate is provided,
953 or a bad certificate is provided, the session is immediately terminated.
955 Note that a valid client certificate is required in order to use the
956 SASL EXTERNAL authentication mechanism with a TLS session. As such,
958 .B olcTLSVerifyClient
959 setting must be chosen to enable SASL EXTERNAL authentication.
962 .B olcTLSCRLCheck: <level>
963 Specifies if the Certificate Revocation List (CRL) of the CA should be
964 used to verify if the client certificates have not been revoked. This
966 .B olcTLSCACertificatePath
967 parameter to be set. This parameter is ignored with GnuTLS and Mozilla NSS.
969 can be specified as one of the following keywords:
973 No CRL checks are performed
976 Check the CRL of the peer certificate
979 Check the CRL for a whole certificate chain
982 .B olcTLSCRLFile: <filename>
983 Specifies a file containing a Certificate Revocation List to be used
984 for verifying that certificates have not been revoked. This parameter
985 is only valid when using GnuTLS or Mozilla NSS.
986 .SH DYNAMIC MODULE OPTIONS
989 is compiled with \-\-enable\-modules then the module-related entries will
990 be available. These entries are named
991 .B cn=module{x},cn=config
993 must have the olcModuleList objectClass. One entry should be created
996 Normally the config engine generates the "{x}" index in the RDN
997 automatically, so it can be omitted when initially loading these entries.
999 .B olcModuleLoad: <filename>
1000 Specify the name of a dynamically loadable module to load. The filename
1001 may be an absolute path name or a simple filename. Non-absolute names
1002 are searched for in the directories specified by the
1006 .B olcModulePath: <pathspec>
1007 Specify a list of directories to search for loadable modules. Typically
1008 the path is colon-separated but this depends on the operating system.
1009 The default is MODULEDIR, which is where the standard OpenLDAP install
1010 will place its modules.
1012 Schema definitions are created as entries in the
1013 .B cn=schema,cn=config
1014 subtree. These entries must have the olcSchemaConfig objectClass.
1015 As noted above, the actual
1016 .B cn=schema,cn=config
1017 entry is predefined and any values specified for it are ignored.
1021 .B olcAttributetypes: "(\ <oid>\
1023 [DESC\ <description>]\
1032 [NO\-USER\-MODIFICATION]\
1033 [USAGE\ <attributeUsage>]\ )"
1035 Specify an attribute type using the LDAPv3 syntax defined in RFC 4512.
1036 The slapd parser extends the RFC 4512 definition by allowing string
1037 forms as well as numeric OIDs to be used for the attribute OID and
1038 attribute syntax OID.
1040 .B olcObjectIdentifier
1046 .B olcDitContentRules: "(\ <oid>\
1048 [DESC\ <description>]\
1055 Specify an DIT Content Rule using the LDAPv3 syntax defined in RFC 4512.
1056 The slapd parser extends the RFC 4512 definition by allowing string
1057 forms as well as numeric OIDs to be used for the attribute OID and
1058 attribute syntax OID.
1060 .B olcObjectIdentifier
1066 .B olcObjectClasses: "(\ <oid>\
1068 [DESC\ <description>]\
1071 [{ ABSTRACT | STRUCTURAL | AUXILIARY }]\
1072 [MUST\ <oids>] [MAY\ <oids>] )"
1074 Specify an objectclass using the LDAPv3 syntax defined in RFC 4512.
1075 The slapd parser extends the RFC 4512 definition by allowing string
1076 forms as well as numeric OIDs to be used for the object class OID.
1080 description.) Object classes are "STRUCTURAL" by default.
1083 .B olcObjectIdentifier: <name> "{ <oid> | <name>[:<suffix>] }"
1084 Define a string name that equates to the given OID. The string can be used
1085 in place of the numeric OID in objectclass and attribute definitions. The
1086 name can also be used with a suffix of the form ":xx" in which case the
1087 value "oid.xx" will be used.
1089 .SH GENERAL BACKEND OPTIONS
1090 Options in these entries only apply to the configuration of a single
1091 type of backend. All backends may support this class of options, but
1093 The entry must be named
1094 .B olcBackend=<databasetype>,cn=config
1095 and must have the olcBackendConfig objectClass.
1115 At present, no backend implements any options of this type, so this
1116 entry should not be used.
1118 .SH DATABASE OPTIONS
1119 Database options are set in entries named
1120 .B olcDatabase={x}<databasetype>,cn=config
1121 and must have the olcDatabaseConfig objectClass. Normally the config
1122 engine generates the "{x}" index in the RDN automatically, so it
1123 can be omitted when initially loading these entries.
1125 The special frontend database is always numbered "{\-1}" and the config
1126 database is always numbered "{0}".
1128 .SH GLOBAL DATABASE OPTIONS
1129 Options in this section may be set in the special "frontend" database
1130 and inherited in all the other databases. These options may be altered
1131 by further settings in each specific database. The frontend entry must
1133 .B olcDatabase=frontend,cn=config
1134 and must have the olcFrontendConfig objectClass.
1136 .B olcAccess: to <what> "[ by <who> <access> <control> ]+"
1137 Grant access (specified by <access>) to a set of entries and/or
1138 attributes (specified by <what>) by one or more requestors (specified
1140 If no access controls are present, the default policy
1141 allows anyone and everyone to read anything but restricts
1142 updates to rootdn. (e.g., "olcAccess: to * by * read").
1144 .BR slapd.access (5)
1145 and the "OpenLDAP Administrator's Guide" for details.
1147 Access controls set in the frontend are appended to any access
1148 controls set on the specific databases.
1149 The rootdn of a database can always read and write EVERYTHING
1152 Extra special care must be taken with the access controls on the
1153 config database. Unlike other databases, the default policy for the
1154 config database is to only allow access to the rootdn. Regular users
1155 should not have read access, and write access should be granted very
1156 carefully to privileged administrators.
1159 .B olcDefaultSearchBase: <dn>
1160 Specify a default search base to use when client submits a
1161 non-base search request with an empty base DN.
1162 Base scoped search requests with an empty base DN are not affected.
1163 This setting is only allowed in the frontend entry.
1165 .B olcExtraAttrs: <attr>
1166 Lists what attributes need to be added to search requests.
1167 Local storage backends return the entire entry to the frontend.
1168 The frontend takes care of only returning the requested attributes
1169 that are allowed by ACLs.
1170 However, features like access checking and so may need specific
1171 attributes that are not automatically returned by remote storage
1172 backends, like proxy backends and so on.
1174 is an attribute that is needed for internal purposes
1175 and thus always needs to be collected, even when not explicitly
1176 requested by clients.
1177 This attribute is multi-valued.
1179 .B olcPasswordHash: <hash> [<hash>...]
1180 This option configures one or more hashes to be used in generation of user
1181 passwords stored in the userPassword attribute during processing of
1182 LDAP Password Modify Extended Operations (RFC 3062).
1183 The <hash> must be one of
1197 use the SHA-1 algorithm (FIPS 160-1), the latter with a seed.
1202 use the MD5 algorithm (RFC 1321), the latter with a seed.
1209 indicates that the new password should be
1210 added to userPassword as clear text.
1212 Note that this option does not alter the normal user applications
1213 handling of userPassword during LDAP Add, Modify, or other LDAP operations.
1214 This setting is only allowed in the frontend entry.
1216 .B olcReadOnly: TRUE | FALSE
1217 This option puts the database into "read-only" mode. Any attempts to
1218 modify the database will return an "unwilling to perform" error. By
1219 default, olcReadOnly is FALSE. Note that when this option is set
1220 TRUE on the frontend, it cannot be reset without restarting the
1221 server, since further writes to the config database will be rejected.
1223 .B olcRequires: <conditions>
1224 Specify a set of conditions to require (default none).
1225 The directive may be specified globally and/or per-database;
1226 databases inherit global conditions, so per-database specifications
1229 requires bind operation prior to directory operations.
1231 requires session to be using LDAP version 3.
1233 requires authentication prior to directory operations.
1235 requires SASL authentication prior to directory operations.
1237 requires strong authentication prior to directory operations.
1238 The strong keyword allows protected "simple" authentication
1239 as well as SASL authentication.
1241 may be used to require no conditions (useful to clear out globally
1242 set conditions within a particular database); it must occur first
1243 in the list of conditions.
1245 .B olcRestrict: <oplist>
1246 Specify a list of operations that are restricted.
1247 Restrictions on a specific database override any frontend setting.
1248 Operations can be any of
1253 .BR extended[=<OID>] ,
1257 or the special pseudo-operations
1261 which respectively summarize read and write operations.
1265 .I olcReadOnly: TRUE
1269 keyword allows to indicate the OID of the specific operation
1272 .B olcSchemaDN: <dn>
1273 Specify the distinguished name for the subschema subentry that
1274 controls the entries on this server. The default is "cn=Subschema".
1276 .B olcSecurity: <factors>
1277 Specify a set of security strength factors (separated by white space)
1279 .BR olcSaslSecprops 's
1281 option for a description of security strength factors).
1282 The directive may be specified globally and/or per-database.
1284 specifies the overall security strength factor.
1286 specifies the transport security strength factor.
1288 specifies the TLS security strength factor.
1290 specifies the SASL security strength factor.
1292 specifies the overall security strength factor to require for
1294 .B update_transport=<n>
1295 specifies the transport security strength factor to require for
1298 specifies the TLS security strength factor to require for
1301 specifies the SASL security strength factor to require for
1304 specifies the security strength factor required for
1306 username/password authentication.
1309 factor is measure of security provided by the underlying transport,
1310 e.g. ldapi:// (and eventually IPSEC). It is not normally used.
1312 .B olcSizeLimit: {<integer>|unlimited}
1314 .B olcSizeLimit: size[.{soft|hard|unchecked}]=<integer> [...]
1315 Specify the maximum number of entries to return from a search operation.
1316 The default size limit is 500.
1319 to specify no limits.
1320 The second format allows a fine grain setting of the size limits.
1321 Extra args can be added in the same value or as additional values.
1324 for an explanation of the different flags.
1326 .B olcSortVals: <attr> [...]
1327 Specify a list of multi-valued attributes whose values will always
1328 be maintained in sorted order. Using this option will allow Modify,
1329 Compare, and filter evaluations on these attributes to be performed
1330 more efficiently. The resulting sort order depends on the
1331 attributes' syntax and matching rules and may not correspond to
1332 lexical order or any other recognizable order.
1333 This setting is only allowed in the frontend entry.
1335 .B olcTimeLimit: {<integer>|unlimited}
1337 .B olcTimeLimit: time[.{soft|hard}]=<integer> [...]
1338 Specify the maximum number of seconds (in real time)
1340 will spend answering a search request. The default time limit is 3600.
1343 to specify no limits.
1344 The second format allows a fine grain setting of the time limits.
1345 Extra args can be added in the same value or as additional values.
1348 for an explanation of the different flags.
1350 .SH GENERAL DATABASE OPTIONS
1351 Options in this section only apply to the specific database for
1352 which they are defined. They are supported by every
1353 type of backend. All of the Global Database Options may also be
1356 .B olcAddContentAcl: TRUE | FALSE
1357 Controls whether Add operations will perform ACL checks on
1358 the content of the entry being added. This check is off
1360 .BR slapd.access (5)
1361 manual page for more details on ACL requirements for
1364 .B olcHidden: TRUE | FALSE
1365 Controls whether the database will be used to answer
1366 queries. A database that is hidden will never be
1367 selected to answer any queries, and any suffix configured
1368 on the database will be ignored in checks for conflicts
1369 with other databases. By default, olcHidden is FALSE.
1371 .B olcLastMod: TRUE | FALSE
1374 will automatically maintain the
1375 modifiersName, modifyTimestamp, creatorsName, and
1376 createTimestamp attributes for entries. It also controls
1377 the entryCSN and entryUUID attributes, which are needed
1378 by the syncrepl provider. By default, olcLastMod is TRUE.
1380 .B olcLimits: <selector> <limit> [<limit> [...]]
1381 Specify time and size limits based on the operation's initiator or
1389 anonymous | users | [<dnspec>=]<pattern> | group[/oc[/at]]=<pattern>
1395 <dnspec> ::= dn[.<type>][.<style>]
1397 <type> ::= self | this
1399 <style> ::= exact | base | onelevel | subtree | children | regex | anonymous
1404 is the default and means the bound user, while
1406 means the base DN of the operation.
1409 matches all unauthenticated clients.
1412 matches all authenticated clients;
1415 dn pattern is assumed unless otherwise specified by qualifying
1416 the (optional) key string
1422 (which are synonyms), to require an exact match; with
1424 to require exactly one level of depth match; with
1426 to allow any level of depth match, including the exact match; with
1428 to allow any level of depth match, not including the exact match;
1430 explicitly requires the (default) match based on POSIX (''extended'')
1431 regular expression pattern.
1434 matches unbound operations; the
1437 The same behavior is obtained by using the
1444 with the optional objectClass
1450 sets the limits for any DN listed in the values of the
1456 group objectClass (default
1458 whose DN exactly matches
1461 The currently supported limits are
1466 The syntax for time limits is
1467 .BR time[.{soft|hard}]=<integer> ,
1470 is the number of seconds slapd will spend answering a search request.
1471 If no time limit is explicitly requested by the client, the
1473 limit is used; if the requested time limit exceeds the
1476 .\".I "Administrative limit exceeded"
1477 .\"error is returned.
1478 limit, the value of the limit is used instead.
1481 limit is set to the keyword
1483 the soft limit is used in either case; if it is set to the keyword
1485 no hard limit is enforced.
1486 Explicit requests for time limits smaller or equal to the
1489 If no limit specifier is set, the value is assigned to the
1495 to preserve the original behavior.
1497 The syntax for size limits is
1498 .BR size[.{soft|hard|unchecked}]=<integer> ,
1501 is the maximum number of entries slapd will return answering a search
1503 If no size limit is explicitly requested by the client, the
1505 limit is used; if the requested size limit exceeds the
1508 .\".I "Administrative limit exceeded"
1509 .\"error is returned.
1510 limit, the value of the limit is used instead.
1513 limit is set to the keyword
1515 the soft limit is used in either case; if it is set to the keyword
1517 no hard limit is enforced.
1518 Explicit requests for size limits smaller or equal to the
1523 specifier sets a limit on the number of candidates a search request is allowed
1525 The rationale behind it is that searches for non-properly indexed
1526 attributes may result in large sets of candidates, which must be
1529 to determine whether they match the search filter or not.
1532 limit provides a means to drop such operations before they are even
1534 If the selected candidates exceed the
1536 limit, the search will abort with
1537 .IR "Unwilling to perform" .
1538 If it is set to the keyword
1540 no limit is applied (the default).
1543 the search is not even performed; this can be used to disallow searches
1544 for a specific set of users.
1545 If no limit specifier is set, the value is assigned to the
1551 to preserve the original behavior.
1553 In case of no match, the global limits are used.
1554 The default values are the same as for
1563 control is requested, the
1565 size limit is used by default, because the request of a specific page size
1566 is considered an explicit request for a limitation on the number
1567 of entries to be returned.
1568 However, the size limit applies to the total count of entries returned within
1569 the search, and not to a single page.
1570 Additional size limits may be enforced; the syntax is
1571 .BR size.pr={<integer>|noEstimate|unlimited} ,
1574 is the max page size if no explicit limit is set; the keyword
1576 inhibits the server from returning an estimate of the total number
1577 of entries that might be returned
1578 (note: the current implementation does not return any estimate).
1581 indicates that no limit is applied to the pagedResults control page size.
1583 .B size.prtotal={<integer>|unlimited|disabled}
1584 allows to set a limit on the total number of entries that a pagedResults
1585 control allows to return.
1586 By default it is set to the
1591 is the max number of entries that the whole search with pagedResults control
1595 to allow unlimited number of entries to be returned, e.g. to allow
1596 the use of the pagedResults control as a means to circumvent size
1597 limitations on regular searches; the keyword
1599 disables the control, i.e. no paged results can be returned.
1600 Note that the total number of entries returned when the pagedResults control
1601 is requested cannot exceed the
1603 size limit of regular searches unless extended by the
1608 .B olcMaxDerefDepth: <depth>
1609 Specifies the maximum number of aliases to dereference when trying to
1610 resolve an entry, used to avoid infinite alias loops. The default is 15.
1612 .B olcMirrorMode: TRUE | FALSE
1613 This option puts a replica database into "mirror" mode. Update
1614 operations will be accepted from any user, not just the updatedn. The
1615 database must already be configured as syncrepl consumer
1616 before this keyword may be set. This mode also requires a
1618 (see above) to be configured.
1619 By default, this setting is FALSE.
1621 .B olcPlugin: <plugin_type> <lib_path> <init_function> [<arguments>]
1622 Configure a SLAPI plugin. See the
1623 .BR slapd.plugin (5)
1624 manpage for more details.
1627 Specify the distinguished name that is not subject to access control
1628 or administrative limit restrictions for operations on this database.
1629 This DN may or may not be associated with an entry. An empty root
1630 DN (the default) specifies no root access is to be granted. It is
1631 recommended that the rootdn only be specified when needed (such as
1632 when initially populating a database). If the rootdn is within
1633 a namingContext (suffix) of the database, a simple bind password
1634 may also be provided using the
1636 directive. Note that the rootdn is always needed when using syncrepl.
1641 database defaults to
1645 .B olcRootPW: <password>
1646 Specify a password (or hash of the password) for the rootdn. The
1647 password can only be set if the rootdn is within the namingContext
1648 (suffix) of the database.
1649 This option accepts all RFC 2307 userPassword formats known to
1652 description) as well as cleartext.
1654 may be used to generate a hash of a password. Cleartext
1655 and \fB{CRYPT}\fP passwords are not recommended. If empty
1656 (the default), authentication of the root DN is by other means
1657 (e.g. SASL). Use of SASL is encouraged.
1659 .B olcSubordinate: [TRUE | FALSE | advertise]
1660 Specify that the current backend database is a subordinate of another
1661 backend database. A subordinate database may have only one suffix. This
1662 option may be used to glue multiple databases into a single namingContext.
1663 If the suffix of the current database is within the namingContext of a
1664 superior database, searches against the superior database will be
1665 propagated to the subordinate as well. All of the databases
1666 associated with a single namingContext should have identical rootdns.
1667 Behavior of other LDAP operations is unaffected by this setting. In
1668 particular, it is not possible to use moddn to move an entry from
1669 one subordinate to another subordinate within the namingContext.
1671 If the optional \fBadvertise\fP flag is supplied, the naming context of
1672 this database is advertised in the root DSE. The default is to hide this
1673 database context, so that only the superior context is visible.
1680 are used on the superior database, any glued subordinates that support
1681 these tools are opened as well.
1683 Databases that are glued together should usually be configured with the
1684 same indices (assuming they support indexing), even for attributes that
1685 only exist in some of these databases. In general, all of the glued
1686 databases should be configured as similarly as possible, since the intent
1687 is to provide the appearance of a single directory.
1689 Note that the subordinate functionality is implemented internally
1690 by the \fIglue\fP overlay and as such its behavior will interact with other
1691 overlays in use. By default, the glue overlay is automatically configured as
1692 the last overlay on the superior database. Its position on the database
1693 can be explicitly configured by setting an \fBoverlay glue\fP directive
1694 at the desired position. This explicit configuration is necessary e.g.
1695 when using the \fIsyncprov\fP overlay, which needs to follow \fIglue\fP
1696 in order to work over all of the glued databases. E.g.
1699 dn: olcDatabase={1}bdb,cn=config
1700 olcSuffix: dc=example,dc=com
1703 dn: olcOverlay={0}glue,olcDatabase={1}bdb,cn=config
1706 dn: olcOverlay={1}syncprov,olcDatabase={1}bdb,cn=config
1710 See the Overlays section below for more details.
1712 .B olcSuffix: <dn suffix>
1713 Specify the DN suffix of queries that will be passed to this
1714 backend database. Multiple suffix lines can be given and at least one is
1715 required for each database definition.
1717 If the suffix of one database is "inside" that of another, the database
1718 with the inner suffix must come first in the configuration file.
1719 You may also want to glue such databases together with the
1723 .B olcSyncUseSubentry: TRUE | FALSE
1724 Store the syncrepl contextCSN in a subentry instead of the context entry
1725 of the database. The subentry's RDN will be "cn=ldapsync". The default is
1726 FALSE, meaning the contextCSN is stored in the context entry.
1729 .B olcSyncrepl: rid=<replica ID>
1730 .B provider=ldap[s]://<hostname>[:port]
1731 .B searchbase=<base DN>
1732 .B [type=refreshOnly|refreshAndPersist]
1733 .B [interval=dd:hh:mm:ss]
1734 .B [retry=[<retry interval> <# of retries>]+]
1735 .B [filter=<filter str>]
1736 .B [scope=sub|one|base|subord]
1737 .B [attrs=<attr list>]
1738 .B [exattrs=<attr list>]
1740 .B [sizelimit=<limit>]
1741 .B [timelimit=<limit>]
1742 .B [schemachecking=on|off]
1743 .B [network\-timeout=<seconds>]
1744 .B [timeout=<seconds>]
1745 .B [bindmethod=simple|sasl]
1747 .B [saslmech=<mech>]
1748 .B [authcid=<identity>]
1749 .B [authzid=<identity>]
1750 .B [credentials=<passwd>]
1752 .B [secprops=<properties>]
1753 .B [keepalive=<idle>:<probes>:<interval>]
1754 .B [starttls=yes|critical]
1755 .B [tls_cert=<file>]
1757 .B [tls_cacert=<file>]
1758 .B [tls_cacertdir=<path>]
1759 .B [tls_reqcert=never|allow|try|demand]
1760 .B [tls_ciphersuite=<ciphers>]
1761 .B [tls_crlcheck=none|peer|all]
1762 .B [suffixmassage=<real DN>]
1763 .B [logbase=<base DN>]
1764 .B [logfilter=<filter str>]
1765 .B [syncdata=default|accesslog|changelog]
1767 Specify the current database as a replica which is kept up-to-date with the
1768 master content by establishing the current
1770 as a replication consumer site running a
1773 The replica content is kept synchronized to the master content using
1774 the LDAP Content Synchronization protocol. Refer to the
1775 "OpenLDAP Administrator's Guide" for detailed information on
1776 setting up a replicated
1778 directory service using the
1783 identifies the current
1785 directive within the replication consumer site.
1786 It is a non-negative integer having no more than three decimal digits.
1789 specifies the replication provider site containing the master content
1790 as an LDAP URI. If <port> is not given, the standard LDAP port number
1791 (389 or 636) is used.
1795 replica is defined using a search
1796 specification as its result set. The consumer
1798 will send search requests to the provider
1800 according to the search specification. The search specification includes
1801 .B searchbase, scope, filter, attrs, attrsonly, sizelimit,
1804 parameters as in the normal search specification. The
1806 option may also be used to specify attributes that should be omitted
1807 from incoming entries.
1808 The \fBscope\fP defaults to \fBsub\fP, the \fBfilter\fP defaults to
1809 \fB(objectclass=*)\fP, and there is no default \fBsearchbase\fP. The
1810 \fBattrs\fP list defaults to \fB"*,+"\fP to return all user and operational
1811 attributes, and \fBattrsonly\fP and \fBexattrs\fP are unset by default.
1812 The \fBsizelimit\fP and \fBtimelimit\fP only
1813 accept "unlimited" and positive integers, and both default to "unlimited".
1814 Note, however, that any provider-side limits for the replication identity
1815 will be enforced by the provider regardless of the limits requested
1816 by the LDAP Content Synchronization operation, much like for any other
1819 The LDAP Content Synchronization protocol has two operation types.
1822 operation, the next synchronization search operation
1823 is periodically rescheduled at an interval time (specified by
1825 parameter; 1 day by default)
1826 after each synchronization operation finishes.
1828 .B refreshAndPersist
1829 operation, a synchronization search remains persistent in the provider slapd.
1830 Further updates to the master replica will generate
1831 .B searchResultEntry
1832 to the consumer slapd as the search responses to the persistent
1833 synchronization search.
1835 If an error occurs during replication, the consumer will attempt to
1836 reconnect according to the
1838 parameter which is a list of the <retry interval> and <# of retries> pairs.
1839 For example, retry="60 10 300 3" lets the consumer retry every 60 seconds
1840 for the first 10 times and then retry every 300 seconds for the next 3
1841 times before stop retrying. The `+' in <# of retries> means indefinite
1842 number of retries until success.
1844 The schema checking can be enforced at the LDAP Sync
1845 consumer site by turning on the
1847 parameter. The default is off.
1851 parameter sets how long the consumer will wait to establish a
1852 network connection to the provider. Once a connection is
1855 parameter determines how long the consumer will wait for the initial
1856 Bind request to complete. The defaults for these parameters come
1864 requires the options
1868 and should only be used when adequate security services
1869 (e.g. TLS or IPSEC) are in place.
1876 Depending on the mechanism, an authentication identity and/or
1877 credentials can be specified using
1883 parameter may be used to specify an authorization identity.
1884 Specific security properties (as with the
1886 keyword above) for a SASL bind can be set with the
1888 option. A non default SASL realm can be set with the
1891 The provider, other than allow authentication of the syncrepl identity,
1892 should grant that identity appropriate access privileges to the data
1893 that is being replicated (\fBaccess\fP directive), and appropriate time
1894 and size limits (\fBlimits\fP directive).
1898 parameter sets the values of \fIidle\fP, \fIprobes\fP, and \fIinterval\fP
1899 used to check whether a socket is alive;
1901 is the number of seconds a connection needs to remain idle before TCP
1902 starts sending keepalive probes;
1904 is the maximum number of keepalive probes TCP should send before dropping
1907 is interval in seconds between individual keepalive probes.
1908 Only some systems support the customization of these values;
1911 parameter is ignored otherwise, and system-wide settings are used.
1915 parameter specifies use of the StartTLS extended operation
1916 to establish a TLS session before Binding to the provider. If the
1918 argument is supplied, the session will be aborted if the StartTLS request
1919 fails. Otherwise the syncrepl session continues without TLS. The
1920 tls_reqcert setting defaults to "demand" and the other TLS settings
1921 default to the same as the main slapd TLS settings.
1925 parameter allows the consumer to pull entries from a remote directory
1926 whose DN suffix differs from the local directory. The portion of the
1927 remote entries' DNs that matches the \fIsearchbase\fP will be replaced
1928 with the suffixmassage DN.
1930 Rather than replicating whole entries, the consumer can query logs of
1931 data modifications. This mode of operation is referred to as \fIdelta
1932 syncrepl\fP. In addition to the above parameters, the
1936 parameters must be set appropriately for the log that will be used. The
1938 parameter must be set to either "accesslog" if the log conforms to the
1939 .BR slapo\-accesslog (5)
1940 log format, or "changelog" if the log conforms
1941 to the obsolete \fIchangelog\fP format. If the
1943 parameter is omitted or set to "default" then the log parameters are
1947 .B olcUpdateDN: <dn>
1948 This option is only applicable in a slave
1950 It specifies the DN permitted to update (subject to access controls)
1951 the replica. It is only needed in certain push-mode
1952 replication scenarios. Generally, this DN
1958 .B olcUpdateRef: <url>
1959 Specify the referral to pass back when
1961 is asked to modify a replicated local database.
1962 If multiple values are specified, each url is provided.
1964 .SH DATABASE-SPECIFIC OPTIONS
1965 Each database may allow specific configuration options; they are
1966 documented separately in the backends' manual pages. See the
1967 .BR slapd.backends (5)
1968 manual page for an overview of available backends.
1970 An overlay is a piece of
1971 code that intercepts database operations in order to extend or change
1972 them. Overlays are pushed onto
1973 a stack over the database, and so they will execute in the reverse
1974 of the order in which they were configured and the database itself
1975 will receive control last of all.
1977 Overlays must be configured as child entries of a specific database. The
1978 entry's RDN must be of the form
1979 .B olcOverlay={x}<overlaytype>
1980 and the entry must have the olcOverlayConfig objectClass. Normally the
1981 config engine generates the "{x}" index in the RDN automatically, so
1982 it can be omitted when initially loading these entries.
1985 .BR slapd.overlays (5)
1986 manual page for an overview of available overlays.
1989 Here is a short example of a configuration in LDIF suitable for use with
1996 objectClass: olcGlobal
1998 olcPidFile: LOCALSTATEDIR/run/slapd.pid
1999 olcAttributeOptions: x\-hidden lang\-
2001 dn: cn=schema,cn=config
2002 objectClass: olcSchemaConfig
2005 include: file://SYSCONFDIR/schema/core.ldif
2007 dn: olcDatabase=frontend,cn=config
2008 objectClass: olcDatabaseConfig
2009 objectClass: olcFrontendConfig
2010 olcDatabase: frontend
2011 # Subtypes of "name" (e.g. "cn" and "ou") with the
2012 # option ";x\-hidden" can be searched for/compared,
2013 # but are not shown. See \fBslapd.access\fP(5).
2014 olcAccess: to attrs=name;x\-hidden by * =cs
2015 # Protect passwords. See \fBslapd.access\fP(5).
2016 olcAccess: to attrs=userPassword by * auth
2017 # Read access to other attributes and entries.
2018 olcAccess: to * by * read
2020 # set a rootpw for the config database so we can bind.
2021 # deny access to everyone else.
2022 dn: olcDatabase=config,cn=config
2023 objectClass: olcDatabaseConfig
2025 olcRootPW: {SSHA}XKYnrjvGT3wZFQrDD5040US592LxsdLy
2026 olcAccess: to * by * none
2028 dn: olcDatabase=bdb,cn=config
2029 objectClass: olcDatabaseConfig
2030 objectClass: olcBdbConfig
2032 olcSuffix: "dc=our\-domain,dc=com"
2033 # The database directory MUST exist prior to
2034 # running slapd AND should only be accessible
2035 # by the slapd/tools. Mode 0700 recommended.
2036 olcDbDirectory: LOCALSTATEDIR/openldap\-data
2037 # Indices to maintain
2038 olcDbIndex: objectClass eq
2039 olcDbIndex: cn,sn,mail pres,eq,approx,sub
2041 # We serve small clients that do not handle referrals,
2042 # so handle remote lookups on their behalf.
2043 dn: olcDatabase=ldap,cn=config
2044 objectClass: olcDatabaseConfig
2045 objectClass: olcLdapConfig
2048 olcDbUri: ldap://ldap.some\-server.com/
2052 Assuming the above data was saved in a file named "config.ldif" and the
2053 ETCDIR/slapd.d directory has been created, this command will initialize
2057 slapadd \-F ETCDIR/slapd.d \-n 0 \-l config.ldif
2062 "OpenLDAP Administrator's Guide" contains a longer annotated
2063 example of a slapd configuration.
2065 Alternatively, an existing slapd.conf file can be converted to the new
2066 format using slapd or any of the slap tools:
2069 slaptest \-f ETCDIR/slapd.conf \-F ETCDIR/slapd.d
2076 default slapd configuration file
2079 default slapd configuration directory
2083 .BR gnutls\-cli (1),
2084 .BR slapd.access (5),
2085 .BR slapd.backends (5),
2087 .BR slapd.overlays (5),
2088 .BR slapd.plugin (5),
2099 "OpenLDAP Administrator's Guide" (http://www.OpenLDAP.org/doc/admin/)
2100 .SH ACKNOWLEDGEMENTS
projects / openldap / blob