1 .TH SLAPD-CONFIG 5 "RELEASEDATE" "OpenLDAP LDVERSION"
2 .\" Copyright 1998-2010 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 olcExtraAttrs: <attr>
450 Lists what attributes need to be added to search requests.
451 Local storage backends return the entire entry to the frontend.
452 The frontend takes care of only returning the requested attributes
453 that are allowed by ACLs.
454 However, features like access checking and so may need specific
455 attributes that are not automatically returned by remote storage
456 backends, like proxy backends and so on.
458 is an attribute that is needed for internal purposes
459 and thus always needs to be collected, even when not explicitly
460 requested by clients.
461 This attribute is multi-valued.
463 .B olcGentleHUP: { TRUE | FALSE }
464 A SIGHUP signal will only cause a 'gentle' shutdown-attempt:
466 will stop listening for new connections, but will not close the
467 connections to the current clients. Future write operations return
468 unwilling-to-perform, though. Slapd terminates when all clients
469 have closed their connections (if they ever do), or - as before -
470 if it receives a SIGTERM signal. This can be useful if you wish to
471 terminate the server and start a new
474 .B with another database,
475 without disrupting the currently active clients.
476 The default is FALSE. You may wish to use
478 along with this option.
480 .B olcIdleTimeout: <integer>
481 Specify the number of seconds to wait before forcibly closing
482 an idle client connection. A setting of 0 disables this
483 feature. The default is 0. You may also want to set the
487 .B olcIndexIntLen: <integer>
488 Specify the key length for ordered integer indices. The most significant
489 bytes of the binary integer will be used for index keys. The default
490 value is 4, which provides exact indexing for 31 bit values.
491 A floating point representation is used to index too large values.
493 .B olcIndexSubstrIfMaxlen: <integer>
494 Specify the maximum length for subinitial and subfinal indices. Only
495 this many characters of an attribute value will be processed by the
496 indexing functions; any excess characters are ignored. The default is 4.
498 .B olcIndexSubstrIfMinlen: <integer>
499 Specify the minimum length for subinitial and subfinal indices. An
500 attribute value must have at least this many characters in order to be
501 processed by the indexing functions. The default is 2.
503 .B olcIndexSubstrAnyLen: <integer>
504 Specify the length used for subany indices. An attribute value must have
505 at least this many characters in order to be processed. Attribute values
506 longer than this length will be processed in segments of this length. The
507 default is 4. The subany index will also be used in subinitial and
508 subfinal index lookups when the filter string is longer than the
509 .I olcIndexSubstrIfMaxlen
512 .B olcIndexSubstrAnyStep: <integer>
513 Specify the steps used in subany index lookups. This value sets the offset
514 for the segments of a filter string that are processed for a subany index
515 lookup. The default is 2. For example, with the default values, a search
516 using this filter "cn=*abcdefgh*" would generate index lookups for
517 "abcd", "cdef", and "efgh".
520 Note: Indexing support depends on the particular backend in use. Also,
521 changing these settings will generally require deleting any indices that
522 depend on these parameters and recreating them with
526 .B olcLocalSSF: <SSF>
527 Specifies the Security Strength Factor (SSF) to be given local LDAP sessions,
528 such as those to the ldapi:// listener. For a description of SSF values,
530 .BR olcSaslSecProps 's
532 option description. The default is 71.
534 .B olcLogFile: <filename>
535 Specify a file for recording debug log messages. By default these messages
536 only go to stderr and are not recorded anywhere else. Specifying a logfile
537 copies messages to both stderr and the logfile.
539 .B olcLogLevel: <integer> [...]
540 Specify the level at which debugging statements and operation
541 statistics should be syslogged (currently logged to the
543 LOG_LOCAL4 facility).
544 They must be considered subsystems rather than increasingly verbose
546 Some messages with higher priority are logged regardless
547 of the configured loglevel as soon as any logging is configured.
548 Log levels are additive, and available levels are:
559 debug packet handling
563 heavy trace debugging (function args)
567 connection management
571 print out packets sent and received
575 search filter processing
579 configuration file processing
583 access control list processing
587 stats log connections/operations/results
591 stats log entries sent
595 print communication with shell backends
607 \"data indexing (unused)
615 only messages that get logged whatever log level is set
618 The desired log level can be input as a single integer that combines
619 the (ORed) desired levels, both in decimal or in hexadecimal notation,
620 as a list of integers (that are ORed internally),
621 or as a list of the names that are shown between brackets, such that
627 olcLogLevel: 0x80 0x1
628 olcLogLevel: acl trace
634 can be used as a shortcut to enable logging at all levels (equivalent to \-1).
637 or the equivalent integer representation, causes those messages
638 that are logged regardless of the configured olcLogLevel to be logged.
639 In fact, if no olcLogLevel (or a 0 level) is defined, no logging occurs,
642 level is required to have high priority messages logged.
645 .B olcPasswordCryptSaltFormat: <format>
646 Specify the format of the salt passed to
648 when generating {CRYPT} passwords (see
649 .BR olcPasswordHash )
650 during processing of LDAP Password Modify Extended Operations (RFC 3062).
652 This string needs to be in
654 format and may include one (and only one) %s conversion.
655 This conversion will be substituted with a string of random
656 characters from [A\-Za\-z0\-9./]. For example, "%.2s"
657 provides a two character salt and "$1$%.8s" tells some
658 versions of crypt(3) to use an MD5 algorithm and provides
659 8 random characters of salt. The default is "%s", which
660 provides 31 characters of salt.
662 .B olcPidFile: <filename>
663 The (absolute) name of a file that will hold the
665 server's process ID (see
668 .B olcPluginLogFile: <filename>
669 The ( absolute ) name of a file that will contain log
676 .B olcReferral: <url>
677 Specify the referral to pass back when
679 cannot find a local database to handle a request.
680 If multiple values are specified, each url is provided.
682 .B olcReverseLookup: TRUE | FALSE
683 Enable/disable client name unverified reverse lookup (default is
685 if compiled with \-\-enable\-rlookups).
687 .B olcRootDSE: <file>
688 Specify the name of an LDIF(5) file containing user defined attributes
689 for the root DSE. These attributes are returned in addition to the
690 attributes normally produced by slapd.
692 The root DSE is an entry with information about the server and its
693 capabilities, in operational attributes.
694 It has the empty DN, and can be read with e.g.:
696 ldapsearch \-x \-b "" \-s base "+"
698 See RFC 4512 section 5.1 for details.
700 .B olcSaslAuxprops: <plugin> [...]
701 Specify which auxprop plugins to use for authentication lookups. The
702 default is empty, which just uses slapd's internal support. Usually
703 no other auxprop plugins are needed.
705 .B olcSaslHost: <fqdn>
706 Used to specify the fully qualified domain name used for SASL processing.
708 .B olcSaslRealm: <realm>
709 Specify SASL realm. Default is empty.
711 .B olcSaslSecProps: <properties>
712 Used to specify Cyrus SASL security properties.
715 flag (without any other properties) causes the flag properties
716 default, "noanonymous,noplain", to be cleared.
719 flag disables mechanisms susceptible to simple passive attacks.
722 flag disables mechanisms susceptible to active attacks.
725 flag disables mechanisms susceptible to passive dictionary attacks.
728 flag disables mechanisms which support anonymous login.
731 flag require forward secrecy between sessions.
734 require mechanisms which pass client credentials (and allow
735 mechanisms which can pass credentials to do so).
738 property specifies the minimum acceptable
739 .I security strength factor
740 as an integer approximate to effective key length used for
741 encryption. 0 (zero) implies no protection, 1 implies integrity
742 protection only, 56 allows DES or other weak ciphers, 112
743 allows triple DES and other strong ciphers, 128 allows RC4,
744 Blowfish and other modern strong ciphers. The default is 0.
747 property specifies the maximum acceptable
748 .I security strength factor
749 as an integer (see minssf description). The default is INT_MAX.
752 property specifies the maximum security layer receive buffer
753 size allowed. 0 disables security layers. The default is 65536.
755 .B olcServerID: <integer> [<URL>]
756 Specify an integer ID from 0 to 4095 for this server (limited
757 to 3 hexadecimal digits). The ID may also be specified as a
758 hexadecimal ID by prefixing the value with "0x".
760 required when using multimaster replication and each master must have a
761 unique ID. Note that this requirement also applies to separate masters
762 contributing to a glued set of databases.
763 If the URL is provided, this directive may be specified
764 multiple times, providing a complete list of participating servers
765 and their IDs. The fully qualified hostname of each server should be
766 used in the supplied URLs. The IDs are used in the "replica id" field
767 of all CSNs generated by the specified server. The default value is zero.
771 olcServerID: 1 ldap://ldap1.example.com
772 olcServerID: 2 ldap://ldap2.example.com
775 .B olcSockbufMaxIncoming: <integer>
776 Specify the maximum incoming LDAP PDU size for anonymous sessions.
777 The default is 262143.
779 .B olcSockbufMaxIncomingAuth: <integer>
780 Specify the maximum incoming LDAP PDU size for authenticated sessions.
781 The default is 4194303.
783 .B olcTCPBuffer [listener=<URL>] [{read|write}=]<size>
784 Specify the size of the TCP buffer.
785 A global value for both read and write TCP buffers related to any listener
786 is defined, unless the listener is explicitly specified,
787 or either the read or write qualifiers are used.
791 Note that some OS-es implement automatic TCP buffer tuning.
793 .B olcThreads: <integer>
794 Specify the maximum size of the primary thread pool.
795 The default is 16; the minimum value is 2.
797 .B olcToolThreads: <integer>
798 Specify the maximum number of threads to use in tool mode.
799 This should not be greater than the number of CPUs in the system.
802 .B olcWriteTimeout: <integer>
803 Specify the number of seconds to wait before forcibly closing
804 a connection with an outstanding write. This allows recovery from
805 various network hang conditions. A setting of 0 disables this
806 feature. The default is 0.
810 is built with support for Transport Layer Security, there are more options
813 .B olcTLSCipherSuite: <cipher-suite-spec>
814 Permits configuring what ciphers will be accepted and the preference order.
815 <cipher-suite-spec> should be a cipher specification for OpenSSL. Example:
817 olcTLSCipherSuite: HIGH:MEDIUM:+SSLv2
819 To check what ciphers a given spec selects in OpenSSL, use:
822 openssl ciphers \-v <cipher-suite-spec>
825 To obtain the list of ciphers in GNUtls use:
831 .B olcTLSCACertificateFile: <filename>
832 Specifies the file that contains certificates for all of the Certificate
837 .B olcTLSCACertificatePath: <path>
838 Specifies the path of a directory that contains Certificate Authority
839 certificates in separate individual files. Usually only one of this
840 or the olcTLSCACertificateFile is defined. If both are specified, both
841 locations will be used. This directive is not supported
844 .B olcTLSCertificateFile: <filename>
845 Specifies the file that contains the
849 .B olcTLSCertificateKeyFile: <filename>
850 Specifies the file that contains the
852 server private key that matches the certificate stored in the
853 .B olcTLSCertificateFile
854 file. If the private key is protected with a password, the password must
855 be manually typed in when slapd starts. Usually the private key is not
856 protected with a password, to allow slapd to start without manual
858 it is of critical importance that the file is protected carefully.
860 .B olcTLSDHParamFile: <filename>
861 This directive specifies the file that contains parameters for Diffie-Hellman
862 ephemeral key exchange. This is required in order to use a DSA certificate on
863 the server. If multiple sets of parameters are present in the file, all of
864 them will be processed. Note that setting this option may also enable
865 Anonymous Diffie-Hellman key exchanges in certain non-default cipher suites.
866 You should append "!ADH" to your cipher suites if you have changed them
867 from the default, otherwise no certificate exchanges or verification will
868 be done. When using GNUtls these parameters are always generated randomly
869 so this directive is ignored.
871 .B olcTLSRandFile: <filename>
872 Specifies the file to obtain random bits from when /dev/[u]random
873 is not available. Generally set to the name of the EGD/PRNGD socket.
874 The environment variable RANDFILE can also be used to specify the filename.
875 This directive is ignored with GNUtls.
877 .B olcTLSVerifyClient: <level>
878 Specifies what checks to perform on client certificates in an
879 incoming TLS session, if any.
882 can be specified as one of the following keywords:
888 will not ask the client for a certificate.
891 The client certificate is requested. If no certificate is provided,
892 the session proceeds normally. If a bad certificate is provided,
893 it will be ignored and the session proceeds normally.
896 The client certificate is requested. If no certificate is provided,
897 the session proceeds normally. If a bad certificate is provided,
898 the session is immediately terminated.
900 .B demand | hard | true
901 These keywords are all equivalent, for compatibility reasons.
902 The client certificate is requested. If no certificate is provided,
903 or a bad certificate is provided, the session is immediately terminated.
905 Note that a valid client certificate is required in order to use the
906 SASL EXTERNAL authentication mechanism with a TLS session. As such,
908 .B olcTLSVerifyClient
909 setting must be chosen to enable SASL EXTERNAL authentication.
912 .B olcTLSCRLCheck: <level>
913 Specifies if the Certificate Revocation List (CRL) of the CA should be
914 used to verify if the client certificates have not been revoked. This
916 .B olcTLSCACertificatePath
917 parameter to be set. This parameter is ignored with GNUtls.
919 can be specified as one of the following keywords:
923 No CRL checks are performed
926 Check the CRL of the peer certificate
929 Check the CRL for a whole certificate chain
932 .B olcTLSCRLFile: <filename>
933 Specifies a file containing a Certificate Revocation List to be used
934 for verifying that certificates have not been revoked. This parameter
935 is only valid when using GNUtls.
936 .SH DYNAMIC MODULE OPTIONS
939 is compiled with \-\-enable\-modules then the module-related entries will
940 be available. These entries are named
941 .B cn=module{x},cn=config
943 must have the olcModuleList objectClass. One entry should be created
946 Normally the config engine generates the "{x}" index in the RDN
947 automatically, so it can be omitted when initially loading these entries.
949 .B olcModuleLoad: <filename>
950 Specify the name of a dynamically loadable module to load. The filename
951 may be an absolute path name or a simple filename. Non-absolute names
952 are searched for in the directories specified by the
956 .B olcModulePath: <pathspec>
957 Specify a list of directories to search for loadable modules. Typically
958 the path is colon-separated but this depends on the operating system.
959 The default is MODULEDIR, which is where the standard OpenLDAP install
960 will place its modules.
962 Schema definitions are created as entries in the
963 .B cn=schema,cn=config
964 subtree. These entries must have the olcSchemaConfig objectClass.
965 As noted above, the actual
966 .B cn=schema,cn=config
967 entry is predefined and any values specified for it are ignored.
971 .B olcAttributetypes: "(\ <oid>\
973 [DESC\ <description>]\
982 [NO\-USER\-MODIFICATION]\
983 [USAGE\ <attributeUsage>]\ )"
985 Specify an attribute type using the LDAPv3 syntax defined in RFC 4512.
986 The slapd parser extends the RFC 4512 definition by allowing string
987 forms as well as numeric OIDs to be used for the attribute OID and
988 attribute syntax OID.
990 .B olcObjectIdentifier
996 .B olcDitContentRules: "(\ <oid>\
998 [DESC\ <description>]\
1005 Specify an DIT Content Rule using the LDAPv3 syntax defined in RFC 4512.
1006 The slapd parser extends the RFC 4512 definition by allowing string
1007 forms as well as numeric OIDs to be used for the attribute OID and
1008 attribute syntax OID.
1010 .B olcObjectIdentifier
1016 .B olcObjectClasses: "(\ <oid>\
1018 [DESC\ <description>]\
1021 [{ ABSTRACT | STRUCTURAL | AUXILIARY }]\
1022 [MUST\ <oids>] [MAY\ <oids>] )"
1024 Specify an objectclass using the LDAPv3 syntax defined in RFC 4512.
1025 The slapd parser extends the RFC 4512 definition by allowing string
1026 forms as well as numeric OIDs to be used for the object class OID.
1030 description.) Object classes are "STRUCTURAL" by default.
1033 .B olcObjectIdentifier: <name> "{ <oid> | <name>[:<suffix>] }"
1034 Define a string name that equates to the given OID. The string can be used
1035 in place of the numeric OID in objectclass and attribute definitions. The
1036 name can also be used with a suffix of the form ":xx" in which case the
1037 value "oid.xx" will be used.
1039 .SH GENERAL BACKEND OPTIONS
1040 Options in these entries only apply to the configuration of a single
1041 type of backend. All backends may support this class of options.
1042 The entry must be named
1043 .B olcBackend=<databasetype>,cn=config
1044 and must have the olcBackendConfig objectClass.
1062 At present, no backend implements any options of this type.
1064 .SH DATABASE OPTIONS
1065 Database options are set in entries named
1066 .B olcDatabase={x}<databasetype>,cn=config
1067 and must have the olcDatabaseConfig objectClass. Normally the config
1068 engine generates the "{x}" index in the RDN automatically, so it
1069 can be omitted when initially loading these entries.
1071 The special frontend database is always numbered "{\-1}" and the config
1072 database is always numbered "{0}".
1074 .SH GLOBAL DATABASE OPTIONS
1075 Options in this section may be set in the special "frontend" database
1076 and inherited in all the other databases. These options may be altered
1077 by further settings in each specific database. The frontend entry must
1079 .B olcDatabase=frontend,cn=config
1080 and must have the olcFrontendConfig objectClass.
1082 .B olcAccess: to <what> "[ by <who> <access> <control> ]+"
1083 Grant access (specified by <access>) to a set of entries and/or
1084 attributes (specified by <what>) by one or more requestors (specified
1086 If no access controls are present, the default policy
1087 allows anyone and everyone to read anything but restricts
1088 updates to rootdn. (e.g., "olcAccess: to * by * read").
1090 .BR slapd.access (5)
1091 and the "OpenLDAP Administrator's Guide" for details.
1093 Access controls set in the frontend are appended to any access
1094 controls set on the specific databases.
1095 The rootdn of a database can always read and write EVERYTHING
1098 Extra special care must be taken with the access controls on the
1099 config database. Unlike other databases, the default policy for the
1100 config database is to only allow access to the rootdn. Regular users
1101 should not have read access, and write access should be granted very
1102 carefully to privileged administrators.
1105 .B olcDefaultSearchBase: <dn>
1106 Specify a default search base to use when client submits a
1107 non-base search request with an empty base DN.
1108 Base scoped search requests with an empty base DN are not affected.
1109 This setting is only allowed in the frontend entry.
1111 .B olcPasswordHash: <hash> [<hash>...]
1112 This option configures one or more hashes to be used in generation of user
1113 passwords stored in the userPassword attribute during processing of
1114 LDAP Password Modify Extended Operations (RFC 3062).
1115 The <hash> must be one of
1129 use the SHA-1 algorithm (FIPS 160-1), the latter with a seed.
1134 use the MD5 algorithm (RFC 1321), the latter with a seed.
1141 indicates that the new password should be
1142 added to userPassword as clear text.
1144 Note that this option does not alter the normal user applications
1145 handling of userPassword during LDAP Add, Modify, or other LDAP operations.
1146 This setting is only allowed in the frontend entry.
1148 .B olcReadOnly: TRUE | FALSE
1149 This option puts the database into "read-only" mode. Any attempts to
1150 modify the database will return an "unwilling to perform" error. By
1151 default, olcReadOnly is FALSE. Note that when this option is set
1152 TRUE on the frontend, it cannot be reset without restarting the
1153 server, since further writes to the config database will be rejected.
1155 .B olcRequires: <conditions>
1156 Specify a set of conditions to require (default none).
1157 The directive may be specified globally and/or per-database;
1158 databases inherit global conditions, so per-database specifications
1161 requires bind operation prior to directory operations.
1163 requires session to be using LDAP version 3.
1165 requires authentication prior to directory operations.
1167 requires SASL authentication prior to directory operations.
1169 requires strong authentication prior to directory operations.
1170 The strong keyword allows protected "simple" authentication
1171 as well as SASL authentication.
1173 may be used to require no conditions (useful to clear out globally
1174 set conditions within a particular database); it must occur first
1175 in the list of conditions.
1177 .B olcRestrict: <oplist>
1178 Specify a list of operations that are restricted.
1179 Restrictions on a specific database override any frontend setting.
1180 Operations can be any of
1185 .BR extended[=<OID>] ,
1189 or the special pseudo-operations
1193 which respectively summarize read and write operations.
1197 .I olcReadOnly: TRUE
1201 keyword allows to indicate the OID of the specific operation
1204 .B olcSchemaDN: <dn>
1205 Specify the distinguished name for the subschema subentry that
1206 controls the entries on this server. The default is "cn=Subschema".
1208 .B olcSecurity: <factors>
1209 Specify a set of security strength factors (separated by white space)
1211 .BR olcSaslSecprops 's
1213 option for a description of security strength factors).
1214 The directive may be specified globally and/or per-database.
1216 specifies the overall security strength factor.
1218 specifies the transport security strength factor.
1220 specifies the TLS security strength factor.
1222 specifies the SASL security strength factor.
1224 specifies the overall security strength factor to require for
1226 .B update_transport=<n>
1227 specifies the transport security strength factor to require for
1230 specifies the TLS security strength factor to require for
1233 specifies the SASL security strength factor to require for
1236 specifies the security strength factor required for
1238 username/password authentication.
1241 factor is measure of security provided by the underlying transport,
1242 e.g. ldapi:// (and eventually IPSEC). It is not normally used.
1244 .B olcSizeLimit: {<integer>|unlimited}
1246 .B olcSizeLimit: size[.{soft|hard|unchecked}]=<integer> [...]
1247 Specify the maximum number of entries to return from a search operation.
1248 The default size limit is 500.
1251 to specify no limits.
1252 The second format allows a fine grain setting of the size limits.
1253 Extra args can be added in the same value or as additional values.
1256 for an explanation of the different flags.
1258 .B olcSortVals: <attr> [...]
1259 Specify a list of multi-valued attributes whose values will always
1260 be maintained in sorted order. Using this option will allow Modify,
1261 Compare, and filter evaluations on these attributes to be performed
1262 more efficiently. The resulting sort order depends on the
1263 attributes' syntax and matching rules and may not correspond to
1264 lexical order or any other recognizable order.
1265 This setting is only allowed in the frontend entry.
1267 .B olcTimeLimit: {<integer>|unlimited}
1269 .B olcTimeLimit: time[.{soft|hard}]=<integer> [...]
1270 Specify the maximum number of seconds (in real time)
1272 will spend answering a search request. The default time limit is 3600.
1275 to specify no limits.
1276 The second format allows a fine grain setting of the time limits.
1277 Extra args can be added in the same value or as additional values.
1280 for an explanation of the different flags.
1282 .SH GENERAL DATABASE OPTIONS
1283 Options in this section only apply to the specific database for
1284 which they are defined. They are supported by every
1285 type of backend. All of the Global Database Options may also be
1288 .B olcAddContentAcl: TRUE | FALSE
1289 Controls whether Add operations will perform ACL checks on
1290 the content of the entry being added. This check is off
1292 .BR slapd.access (5)
1293 manual page for more details on ACL requirements for
1296 .B olcHidden: TRUE | FALSE
1297 Controls whether the database will be used to answer
1298 queries. A database that is hidden will never be
1299 selected to answer any queries, and any suffix configured
1300 on the database will be ignored in checks for conflicts
1301 with other databases. By default, olcHidden is FALSE.
1303 .B olcLastMod: TRUE | FALSE
1306 will automatically maintain the
1307 modifiersName, modifyTimestamp, creatorsName, and
1308 createTimestamp attributes for entries. It also controls
1309 the entryCSN and entryUUID attributes, which are needed
1310 by the syncrepl provider. By default, olcLastMod is TRUE.
1312 .B olcLimits: <selector> <limit> [<limit> [...]]
1313 Specify time and size limits based on the operation's initiator or
1321 anonymous | users | [<dnspec>=]<pattern> | group[/oc[/at]]=<pattern>
1327 <dnspec> ::= dn[.<type>][.<style>]
1329 <type> ::= self | this
1331 <style> ::= exact | base | onelevel | subtree | children | regex | anonymous
1336 is the default and means the bound user, while
1338 means the base DN of the operation.
1341 matches all unauthenticated clients.
1344 matches all authenticated clients;
1347 dn pattern is assumed unless otherwise specified by qualifying
1348 the (optional) key string
1354 (which are synonyms), to require an exact match; with
1356 to require exactly one level of depth match; with
1358 to allow any level of depth match, including the exact match; with
1360 to allow any level of depth match, not including the exact match;
1362 explicitly requires the (default) match based on POSIX (''extended'')
1363 regular expression pattern.
1366 matches unbound operations; the
1369 The same behavior is obtained by using the
1376 with the optional objectClass
1382 sets the limits for any DN listed in the values of the
1388 group objectClass (default
1390 whose DN exactly matches
1393 The currently supported limits are
1398 The syntax for time limits is
1399 .BR time[.{soft|hard}]=<integer> ,
1402 is the number of seconds slapd will spend answering a search request.
1403 If no time limit is explicitly requested by the client, the
1405 limit is used; if the requested time limit exceeds the
1408 .\".I "Administrative limit exceeded"
1409 .\"error is returned.
1410 limit, the value of the limit is used instead.
1413 limit is set to the keyword
1415 the soft limit is used in either case; if it is set to the keyword
1417 no hard limit is enforced.
1418 Explicit requests for time limits smaller or equal to the
1421 If no limit specifier is set, the value is assigned to the
1427 to preserve the original behavior.
1429 The syntax for size limits is
1430 .BR size[.{soft|hard|unchecked}]=<integer> ,
1433 is the maximum number of entries slapd will return answering a search
1435 If no size limit is explicitly requested by the client, the
1437 limit is used; if the requested size limit exceeds the
1440 .\".I "Administrative limit exceeded"
1441 .\"error is returned.
1442 limit, the value of the limit is used instead.
1445 limit is set to the keyword
1447 the soft limit is used in either case; if it is set to the keyword
1449 no hard limit is enforced.
1450 Explicit requests for size limits smaller or equal to the
1455 specifier sets a limit on the number of candidates a search request is allowed
1457 The rationale behind it is that searches for non-properly indexed
1458 attributes may result in large sets of candidates, which must be
1461 to determine whether they match the search filter or not.
1464 limit provides a means to drop such operations before they are even
1466 If the selected candidates exceed the
1468 limit, the search will abort with
1469 .IR "Unwilling to perform" .
1470 If it is set to the keyword
1472 no limit is applied (the default).
1475 the search is not even performed; this can be used to disallow searches
1476 for a specific set of users.
1477 If no limit specifier is set, the value is assigned to the
1483 to preserve the original behavior.
1485 In case of no match, the global limits are used.
1486 The default values are the same as for
1495 control is requested, the
1497 size limit is used by default, because the request of a specific page size
1498 is considered an explicit request for a limitation on the number
1499 of entries to be returned.
1500 However, the size limit applies to the total count of entries returned within
1501 the search, and not to a single page.
1502 Additional size limits may be enforced; the syntax is
1503 .BR size.pr={<integer>|noEstimate|unlimited} ,
1506 is the max page size if no explicit limit is set; the keyword
1508 inhibits the server from returning an estimate of the total number
1509 of entries that might be returned
1510 (note: the current implementation does not return any estimate).
1513 indicates that no limit is applied to the pagedResults control page size.
1515 .B size.prtotal={<integer>|unlimited|disabled}
1516 allows to set a limit on the total number of entries that a pagedResults
1517 control allows to return.
1518 By default it is set to the
1523 is the max number of entries that the whole search with pagedResults control
1527 to allow unlimited number of entries to be returned, e.g. to allow
1528 the use of the pagedResults control as a means to circumvent size
1529 limitations on regular searches; the keyword
1531 disables the control, i.e. no paged results can be returned.
1532 Note that the total number of entries returned when the pagedResults control
1533 is requested cannot exceed the
1535 size limit of regular searches unless extended by the
1540 .B olcMaxDerefDepth: <depth>
1541 Specifies the maximum number of aliases to dereference when trying to
1542 resolve an entry, used to avoid infinite alias loops. The default is 15.
1544 .B olcMirrorMode: TRUE | FALSE
1545 This option puts a replica database into "mirror" mode. Update
1546 operations will be accepted from any user, not just the updatedn. The
1547 database must already be configured as syncrepl consumer
1548 before this keyword may be set. This mode also requires a
1550 (see above) to be configured.
1551 By default, this setting is FALSE.
1553 .B olcPlugin: <plugin_type> <lib_path> <init_function> [<arguments>]
1554 Configure a SLAPI plugin. See the
1555 .BR slapd.plugin (5)
1556 manpage for more details.
1559 Specify the distinguished name that is not subject to access control
1560 or administrative limit restrictions for operations on this database.
1561 This DN may or may not be associated with an entry. An empty root
1562 DN (the default) specifies no root access is to be granted. It is
1563 recommended that the rootdn only be specified when needed (such as
1564 when initially populating a database). If the rootdn is within
1565 a namingContext (suffix) of the database, a simple bind password
1566 may also be provided using the
1568 directive. Note that the rootdn is always needed when using syncrepl.
1570 .B olcRootPW: <password>
1571 Specify a password (or hash of the password) for the rootdn. The
1572 password can only be set if the rootdn is within the namingContext
1573 (suffix) of the database.
1574 This option accepts all RFC 2307 userPassword formats known to
1577 description) as well as cleartext.
1579 may be used to generate a hash of a password. Cleartext
1580 and \fB{CRYPT}\fP passwords are not recommended. If empty
1581 (the default), authentication of the root DN is by other means
1582 (e.g. SASL). Use of SASL is encouraged.
1584 .B olcSubordinate: [TRUE | FALSE | advertise]
1585 Specify that the current backend database is a subordinate of another
1586 backend database. A subordinate database may have only one suffix. This
1587 option may be used to glue multiple databases into a single namingContext.
1588 If the suffix of the current database is within the namingContext of a
1589 superior database, searches against the superior database will be
1590 propagated to the subordinate as well. All of the databases
1591 associated with a single namingContext should have identical rootdns.
1592 Behavior of other LDAP operations is unaffected by this setting. In
1593 particular, it is not possible to use moddn to move an entry from
1594 one subordinate to another subordinate within the namingContext.
1596 If the optional \fBadvertise\fP flag is supplied, the naming context of
1597 this database is advertised in the root DSE. The default is to hide this
1598 database context, so that only the superior context is visible.
1605 are used on the superior database, any glued subordinates that support
1606 these tools are opened as well.
1608 Databases that are glued together should usually be configured with the
1609 same indices (assuming they support indexing), even for attributes that
1610 only exist in some of these databases. In general, all of the glued
1611 databases should be configured as similarly as possible, since the intent
1612 is to provide the appearance of a single directory.
1614 Note that the subordinate functionality is implemented internally
1615 by the \fIglue\fP overlay and as such its behavior will interact with other
1616 overlays in use. By default, the glue overlay is automatically configured as
1617 the last overlay on the superior database. Its position on the database
1618 can be explicitly configured by setting an \fBoverlay glue\fP directive
1619 at the desired position. This explicit configuration is necessary e.g.
1620 when using the \fIsyncprov\fP overlay, which needs to follow \fIglue\fP
1621 in order to work over all of the glued databases. E.g.
1624 dn: olcDatabase={1}bdb,cn=config
1625 olcSuffix: dc=example,dc=com
1628 dn: olcOverlay={0}glue,olcDatabase={1}bdb,cn=config
1631 dn: olcOverlay={1}syncprov,olcDatabase={1}bdb,cn=config
1635 See the Overlays section below for more details.
1637 .B olcSuffix: <dn suffix>
1638 Specify the DN suffix of queries that will be passed to this
1639 backend database. Multiple suffix lines can be given and at least one is
1640 required for each database definition.
1642 If the suffix of one database is "inside" that of another, the database
1643 with the inner suffix must come first in the configuration file.
1644 You may also want to glue such databases together with the
1648 .B olcSyncUseSubentry: TRUE | FALSE
1649 Store the syncrepl contextCSN in a subentry instead of the context entry
1650 of the database. The subentry's RDN will be "cn=ldapsync". The default is
1651 FALSE, meaning the contextCSN is stored in the context entry.
1654 .B olcSyncrepl: rid=<replica ID>
1655 .B provider=ldap[s]://<hostname>[:port]
1656 .B searchbase=<base DN>
1657 .B [type=refreshOnly|refreshAndPersist]
1658 .B [interval=dd:hh:mm:ss]
1659 .B [retry=[<retry interval> <# of retries>]+]
1660 .B [filter=<filter str>]
1661 .B [scope=sub|one|base|subord]
1662 .B [attrs=<attr list>]
1663 .B [exattrs=<attr list>]
1665 .B [sizelimit=<limit>]
1666 .B [timelimit=<limit>]
1667 .B [schemachecking=on|off]
1668 .B [network\-timeout=<seconds>]
1669 .B [timeout=<seconds>]
1670 .B [bindmethod=simple|sasl]
1672 .B [saslmech=<mech>]
1673 .B [authcid=<identity>]
1674 .B [authzid=<identity>]
1675 .B [credentials=<passwd>]
1677 .B [secprops=<properties>]
1678 .B [keepalive=<idle>:<probes>:<interval>]
1679 .B [starttls=yes|critical]
1680 .B [tls_cert=<file>]
1682 .B [tls_cacert=<file>]
1683 .B [tls_cacertdir=<path>]
1684 .B [tls_reqcert=never|allow|try|demand]
1685 .B [tls_ciphersuite=<ciphers>]
1686 .B [tls_crlcheck=none|peer|all]
1687 .B [logbase=<base DN>]
1688 .B [logfilter=<filter str>]
1689 .B [syncdata=default|accesslog|changelog]
1691 Specify the current database as a replica which is kept up-to-date with the
1692 master content by establishing the current
1694 as a replication consumer site running a
1697 The replica content is kept synchronized to the master content using
1698 the LDAP Content Synchronization protocol. Refer to the
1699 "OpenLDAP Administrator's Guide" for detailed information on
1700 setting up a replicated
1702 directory service using the
1707 identifies the current
1709 directive within the replication consumer site.
1710 It is a non-negative integer having no more than three decimal digits.
1713 specifies the replication provider site containing the master content
1714 as an LDAP URI. If <port> is not given, the standard LDAP port number
1715 (389 or 636) is used.
1719 replica is defined using a search
1720 specification as its result set. The consumer
1722 will send search requests to the provider
1724 according to the search specification. The search specification includes
1725 .B searchbase, scope, filter, attrs, attrsonly, sizelimit,
1728 parameters as in the normal search specification. The
1730 option may also be used to specify attributes that should be omitted
1731 from incoming entries.
1732 The \fBscope\fP defaults to \fBsub\fP, the \fBfilter\fP defaults to
1733 \fB(objectclass=*)\fP, and there is no default \fBsearchbase\fP. The
1734 \fBattrs\fP list defaults to \fB"*,+"\fP to return all user and operational
1735 attributes, and \fBattrsonly\fP and \fBexattrs\fP are unset by default.
1736 The \fBsizelimit\fP and \fBtimelimit\fP only
1737 accept "unlimited" and positive integers, and both default to "unlimited".
1738 Note, however, that any provider-side limits for the replication identity
1739 will be enforced by the provider regardless of the limits requested
1740 by the LDAP Content Synchronization operation, much like for any other
1743 The LDAP Content Synchronization protocol has two operation types.
1746 operation, the next synchronization search operation
1747 is periodically rescheduled at an interval time (specified by
1749 parameter; 1 day by default)
1750 after each synchronization operation finishes.
1752 .B refreshAndPersist
1753 operation, a synchronization search remains persistent in the provider slapd.
1754 Further updates to the master replica will generate
1755 .B searchResultEntry
1756 to the consumer slapd as the search responses to the persistent
1757 synchronization search.
1759 If an error occurs during replication, the consumer will attempt to
1760 reconnect according to the
1762 parameter which is a list of the <retry interval> and <# of retries> pairs.
1763 For example, retry="60 10 300 3" lets the consumer retry every 60 seconds
1764 for the first 10 times and then retry every 300 seconds for the next 3
1765 times before stop retrying. The `+' in <# of retries> means indefinite
1766 number of retries until success.
1768 The schema checking can be enforced at the LDAP Sync
1769 consumer site by turning on the
1771 parameter. The default is off.
1775 parameter sets how long the consumer will wait to establish a
1776 network connection to the provider. Once a connection is
1779 parameter determines how long the consumer will wait for the initial
1780 Bind request to complete. The defaults for these parameters come
1788 requires the options
1792 and should only be used when adequate security services
1793 (e.g. TLS or IPSEC) are in place.
1800 Depending on the mechanism, an authentication identity and/or
1801 credentials can be specified using
1807 parameter may be used to specify an authorization identity.
1808 Specific security properties (as with the
1810 keyword above) for a SASL bind can be set with the
1812 option. A non default SASL realm can be set with the
1815 The provider, other than allow authentication of the syncrepl identity,
1816 should grant that identity appropriate access privileges to the data
1817 that is being replicated (\fBaccess\fP directive), and appropriate time
1818 and size limits (\fBlimits\fP directive).
1822 parameter sets the values of \fIidle\fP, \fIprobes\fP, and \fIinterval\fP
1823 used to check whether a socket is alive;
1825 is the number of seconds a connection needs to remain idle before TCP
1826 starts sending keepalive probes;
1828 is the maximum number of keepalive probes TCP should send before dropping
1831 is interval in seconds between individual keepalive probes.
1832 Only some systems support the customization of these values;
1835 parameter is ignored otherwise, and system-wide settings are used.
1839 parameter specifies use of the StartTLS extended operation
1840 to establish a TLS session before Binding to the provider. If the
1842 argument is supplied, the session will be aborted if the StartTLS request
1843 fails. Otherwise the syncrepl session continues without TLS. The
1844 tls_reqcert setting defaults to "demand" and the other TLS settings
1845 default to the same as the main slapd TLS settings.
1847 Rather than replicating whole entries, the consumer can query logs of
1848 data modifications. This mode of operation is referred to as \fIdelta
1849 syncrepl\fP. In addition to the above parameters, the
1853 parameters must be set appropriately for the log that will be used. The
1855 parameter must be set to either "accesslog" if the log conforms to the
1856 .BR slapo\-accesslog (5)
1857 log format, or "changelog" if the log conforms
1858 to the obsolete \fIchangelog\fP format. If the
1860 parameter is omitted or set to "default" then the log parameters are
1864 .B olcUpdateDN: <dn>
1865 This option is only applicable in a slave
1867 It specifies the DN permitted to update (subject to access controls)
1868 the replica. It is only needed in certain push-mode
1869 replication scenarios. Generally, this DN
1875 .B olcUpdateRef: <url>
1876 Specify the referral to pass back when
1878 is asked to modify a replicated local database.
1879 If multiple values are specified, each url is provided.
1881 .SH DATABASE-SPECIFIC OPTIONS
1882 Each database may allow specific configuration options; they are
1883 documented separately in the backends' manual pages. See the
1884 .BR slapd.backends (5)
1885 manual page for an overview of available backends.
1887 An overlay is a piece of
1888 code that intercepts database operations in order to extend or change
1889 them. Overlays are pushed onto
1890 a stack over the database, and so they will execute in the reverse
1891 of the order in which they were configured and the database itself
1892 will receive control last of all.
1894 Overlays must be configured as child entries of a specific database. The
1895 entry's RDN must be of the form
1896 .B olcOverlay={x}<overlaytype>
1897 and the entry must have the olcOverlayConfig objectClass. Normally the
1898 config engine generates the "{x}" index in the RDN automatically, so
1899 it can be omitted when initially loading these entries.
1902 .BR slapd.overlays (5)
1903 manual page for an overview of available overlays.
1906 Here is a short example of a configuration in LDIF suitable for use with
1913 objectClass: olcGlobal
1915 olcPidFile: LOCALSTATEDIR/run/slapd.pid
1916 olcAttributeOptions: x\-hidden lang\-
1918 dn: cn=schema,cn=config
1919 objectClass: olcSchemaConfig
1922 include: SYSCONFDIR/schema/core.ldif
1924 dn: olcDatabase=frontend,cn=config
1925 objectClass: olcDatabaseConfig
1926 objectClass: olcFrontendConfig
1927 olcDatabase: frontend
1928 # Subtypes of "name" (e.g. "cn" and "ou") with the
1929 # option ";x\-hidden" can be searched for/compared,
1930 # but are not shown. See \fBslapd.access\fP(5).
1931 olcAccess: to attrs=name;x\-hidden by * =cs
1932 # Protect passwords. See \fBslapd.access\fP(5).
1933 olcAccess: to attrs=userPassword by * auth
1934 # Read access to other attributes and entries.
1935 olcAccess: to * by * read
1937 # set a rootpw for the config database so we can bind.
1938 # deny access to everyone else.
1939 dn: olcDatabase=config,cn=config
1940 objectClass: olcDatabaseConfig
1942 olcRootPW: {SSHA}XKYnrjvGT3wZFQrDD5040US592LxsdLy
1943 olcAccess: to * by * none
1945 dn: olcDatabase=bdb,cn=config
1946 objectClass: olcDatabaseConfig
1947 objectClass: olcBdbConfig
1949 olcSuffix: "dc=our\-domain,dc=com"
1950 # The database directory MUST exist prior to
1951 # running slapd AND should only be accessible
1952 # by the slapd/tools. Mode 0700 recommended.
1953 olcDbDirectory: LOCALSTATEDIR/openldap\-data
1954 # Indices to maintain
1955 olcDbIndex: objectClass eq
1956 olcDbIndex: cn,sn,mail pres,eq,approx,sub
1958 # We serve small clients that do not handle referrals,
1959 # so handle remote lookups on their behalf.
1960 dn: olcDatabase=ldap,cn=config
1961 objectClass: olcDatabaseConfig
1962 objectClass: olcLdapConfig
1965 olcDbUri: ldap://ldap.some\-server.com/
1969 Assuming the above data was saved in a file named "config.ldif" and the
1970 ETCDIR/slapd.d directory has been created, this command will initialize
1974 slapadd \-F ETCDIR/slapd.d \-n 0 \-l config.ldif
1979 "OpenLDAP Administrator's Guide" contains a longer annotated
1980 example of a slapd configuration.
1982 Alternatively, an existing slapd.conf file can be converted to the new
1983 format using slapd or any of the slap tools:
1986 slaptest \-f ETCDIR/slapd.conf \-F ETCDIR/slapd.d
1993 default slapd configuration file
1996 default slapd configuration directory
2000 .BR slapd.access (5),
2001 .BR slapd.backends (5),
2003 .BR slapd.overlays (5),
2004 .BR slapd.plugin (5),
2005 .BR slapd.replog (5),
2016 "OpenLDAP Administrator's Guide" (http://www.OpenLDAP.org/doc/admin/)
2017 .SH ACKNOWLEDGEMENTS
projects / openldap / blob