1 .TH SLAPD.CONF 5 "RELEASEDATE" "OpenLDAP LDVERSION"
2 .\" Copyright 1998-2002 The OpenLDAP Foundation All Rights Reserved.
3 .\" Copying restrictions apply. See COPYRIGHT/LICENSE.
6 slapd.conf \- configuration file for slapd, the stand-alone LDAP daemon
12 contains configuration information for the
14 daemon. This configuration file is also used by the
16 replication daemon and by the SLAPD tools
24 file consists of a series of global configuration options that apply to
26 as a whole (including all backends), followed by zero or more database
27 backend definitions that contain information specific to a backend
35 # comment - these options apply to every database
36 <global configuration options>
37 # first database definition & configuration options
38 database <backend 1 type>
39 <configuration options specific to backend 1>
40 # subsequent database definitions & configuration options
44 As many backend-specific sections as desired may be included. Global
45 options can be overridden in a backend (for options that appear more
46 than once, the last appearance in the
48 file is used). Blank lines and comment lines beginning with a `#'
49 character are ignored. If a line begins with white space, it is
50 considered a continuation of the previous line.
52 Arguments on configuration lines are separated by white space. If an
53 argument contains white space, the argument should be enclosed in
54 double quotes. If an argument contains a double quote (`"') or a
55 backslash character (`\\'), the character should be preceded by a
58 The specific configuration options available are discussed below in the
59 Global Configuration Options, General Backend Options, and General Database
60 Options. Backend-specific options are discussed in the
62 manual pages. Refer to the "OpenLDAP Administrator's Guide" for more
63 details on the slapd configuration file.
64 .SH GLOBAL CONFIGURATION OPTIONS
65 Options described in this section apply to all backends, unless specifically
66 overridden in a backend definition. Arguments that should be replaced by
67 actual text are shown in brackets <>.
69 .B access to <what> "[ by <who> <access> <control> ]+"
70 Grant access (specified by <access>) to a set of entries and/or
71 attributes (specified by <what>) by one or more requestors (specified
75 and the "OpenLDAP's Administrator's Guide" for details.
78 Specify a set of features (separated by white space) to
81 allows acceptance of LDAPv2 bind requests.
83 allows anonymous bind when credentials are not empty (e.g.
86 allows unauthenticated (anonymous) bind when DN is not empty.
88 allow unauthenticated (anonymous) update operations to be processed
89 (subject to access controls and other administrative limits).
91 .B argsfile <filename>
92 The ( absolute ) name of a file that will hold the
94 server's command line options
95 if started without the debugging command line option.
98 .B attributetype "(\ <oid> [NAME\ <name>] [OBSOLETE]\
99 [DESC\ <description>]\
100 [SUP\ <oid>] [EQUALITY\ <oid>] [ORDERING\ <oid>]\
101 [SUBSTR\ <oid>] [SYNTAX\ <oidlen>] [SINGLE\-VALUE] [COLLECTIVE]\
102 [NO\-USER\-MODIFICATION] [USAGE\ <attributeUsage>]\ )"
104 Specify an attribute type using the LDAPv3 syntax defined in RFC 2252.
105 The slapd parser extends the RFC 2252 definition by allowing string
106 forms as well as numeric OIDs to be used for the attribute OID and
107 attribute syntax OID.
113 .B concurrency <integer>
114 Specify a desired level of concurrency. Provided to the underlying
115 thread system as a hint. The default is not to provide any hint.
117 .\".B debug <subsys> <level>
118 .\"Specify a logging level for a particular subsystem. The subsystems include
120 .\"a global level for all subsystems,
124 .\"the backend databases,
126 .\"the entry cache manager,
128 .\"the config file reader,
130 .\"the connection manager,
132 .\"the Cyrus SASL library interface,
134 .\"the search filter processor,
136 .\"the DN normalization library,
138 .\"the database indexer,
140 .\"the ASN.1 BER library,
142 .\"the dynamic module loader,
144 .\"the LDAP operation processors,
146 .\"the SASL authentication subsystem,
148 .\"the schema processor, and
150 .\"the TLS library interface. This is not an exhaustive list; there are many
151 .\"other subsystems and more are added over time.
153 .\"The levels are, in order of decreasing priority:
154 .\".B emergency, alert, critical, error, warning, notice, information, entry,
155 .\".B args, results, detail1, detail2
156 .\"An integer may be used instead, with 0 corresponding to
162 .\"level logs function entry points,
164 .\"adds function call parameters, and
166 .\"adds the function results to the logs.
171 .\"levels add even more low level detail from individual functions.
173 .B defaultsearchbase <dn>
174 Specify a default search base to use when client submits a
175 non-base search request with an empty base DN.
177 .B disallow <features>
178 Specify a set of features (separated by white space) to
179 disallow (default none).
181 disables acceptance of anonymous bind requests.
183 disables simple (bind) authentication.
184 .B bind_simple_unprotected
185 disables simple (bind) authentication when confidentiality
186 protection (e.g. TLS) is not in place. The
190 option provides fine grain control over the confidentiality
191 protection required for simple bind.
193 disables Kerberos V4 (bind) authentication.
195 disables Start TLS from forcing session to anonymous status (see also
198 disables StartTLS if authenticated (see also
201 .B gentlehup { on | off }
202 A SIGHUP signal will only cause a 'gentle' shutdown-attempt:
204 will stop listening for new connections, but will not close the
205 connections to the current clients. Future write operations return
206 unwilling-to-perform, though. Slapd terminates when all clients
207 have closed their connections (if they ever do), or \- as before \-
208 if it receives a SIGTERM signal. This can be useful if you wish to
209 terminate the server and start a new
212 .B with another database,
213 without disrupting the currently active clients.
214 The default is off. You may wish to use
216 along with this option.
218 .B idletimeout <integer>
219 Specify the number of seconds to wait before forcibly closing
220 an idle client connection. A idletimeout of 0 disables this
221 feature. The default is 0.
223 .B include <filename>
224 Read additional configuration information from the given file before
225 continuing with the next line of the current file.
227 .B limits <who> <limit> [<limit> [...]]
228 Specify time and size limits based on who initiated an operation.
235 anonymous | users | [dn[.<style>]=]<pattern>
241 <style> ::= exact | base | one | subtree | children | regex | anonymous
245 is hit when a search is performed without prior binding;
247 is hit when a search is performed by a successfully bound user;
250 dn pattern is assumed unless otherwise specified by qualifying
251 the (optional) key string
257 (which are synonims), to require an exact match; with
259 to require exactly one level of depth match; with
261 to allow any level of depth match, including the exact match; with
263 to allow any level of depth match, not including the exact match;
265 explicitly requires the (default) match based on regular expression
266 pattern, as detailed in
270 matches unbound operations; the
273 The same behavior is obtained by using the
279 The currently supported limits are
284 The syntax for time limits is
285 .BR time[.{soft|hard}]=<integer> ,
288 is the number of seconds slapd will spend answering a search request.
289 If no time limit is explicitly requested by the client, the
291 limit is used; if the requested time limit exceedes the
293 limit, an "Unwilling to perform" is returned.
296 limit is set to 0 or to the keyword "soft", the soft limit is used
297 in either case; if it is set to -1 or to the keyword "none",
298 no hard limit is enforced.
299 Explicit requests for time limits smaller or equal to the
302 If no flag is set, the value is assigned to the
306 limit is set to zero, to preserve the original behavior.
308 The syntax for size limits is
309 .BR size[.{soft|hard|unchecked}]=<integer> ,
312 is the maximum number of entries slapd will return answering a search
314 If no size limit is explicitly requested by the client, the
316 limit is used; if the requested size limit exceedes the
318 limit, an "Unwilling to perform" is returned.
321 limit is set to 0 or to the keyword "soft", the soft limit is used
322 in either case; if it is set to -1 or to the keyword "none",
323 no hard limit is enforced.
324 Explicit requests for size limits smaller or equal to the
329 flag sets a limit on the number of candidates a search request is allowed
331 If the selected candidates exceed the
333 limit, the search will abort with "Unwilling to perform".
334 If it is set to -1 or to the keyword "none", no limit is applied (the default).
335 If no flag is set, the value is assigned to the
339 limit is set to zero, to preserve the original behavior.
341 In case of no match, the global limits are used.
342 The default values are the same of
350 .\".B logfile <filename>
351 .\"Specify a file for recording debug log messages. By default these messages
352 .\"only go to stderr and are not recorded anywhere else. Specifying a logfile
353 .\"copies messages to both stderr and the logfile.
355 .B loglevel <integer>
356 Specify the level at which debugging statements and operation
357 statistics should be syslogged (currently logged to the
359 LOG_LOCAL4 facility). Log levels are additive, and available levels
369 debug packet handling
372 heavy trace debugging
375 connection management
378 print out packets sent and received
381 search filter processing
384 configuration file processing
387 access control list processing
390 stats log connections/operations/results
393 stats log entries sent
396 print communication with shell backends
404 .B moduleload <filename>
405 Specify the name of a dynamically loadable module to load. The filename
406 may be an absolute path name or a simple filename. Non-absolute names
407 are searched for in the directories specified by the
409 option. This option and the
411 option are only usable if slapd was compiled with --enable-modules.
413 .B modulepath <pathspec>
414 Specify a list of directories to search for loadable modules. Typically
415 the path is colon-separated but this depends on the operating system.
417 .B objectclass "( <oid> [NAME <name>] [DESC <description] [OBSOLETE]\
418 [SUP <oids>] [{ ABSTRACT | STRUCTURAL | AUXILIARY }] [MUST <oids>]\
421 Specify an objectclass using the LDAPv3 syntax defined in RFC 2252.
422 The slapd parser extends the RFC 2252 definition by allowing string
423 forms as well as numeric OIDs to be used for the object class OID.
427 description.) Object classes are "STRUCTURAL" by default.
430 .B objectidentifier <name> "{ <oid> | <name>[:<suffix>] }"
431 Define a string name that equates to the given OID. The string can be used
432 in place of the numeric OID in objectclass and attribute definitions. The
433 name can also be used with a suffix of the form ":xx" in which case the
434 value "oid.xx" will be used.
436 .B password-hash <hash>
437 This option sets the hash to be used in generation of user
438 passwords, stored in userPassword, during processing of
439 LDAP Password Modify Extended Operations (RFC 3052).
440 The <hash> must be one of
454 use the SHA-1 algorithm (FIPS 160-1), the latter with a seed.
459 use the MD5 algorithm (RFC 1321), the latter with a seed.
466 indicates that the new password should be
467 added to userPassword as clear text.
469 Note that this option does not alter the normal user applications
470 handling of userPassword during LDAP Add, Modify, or other LDAP operations.
472 .B password\-crypt\-salt\-format <format>
473 Specify the format of the salt passed to
475 when generating {CRYPT} passwords (see
477 during processing of LDAP Password Modify Extended Operations (RFC 3062).
479 This string needs to be in
481 format and may include one (and only one) %s conversion.
482 This conversion will be substituted with a string random
483 characters from [A\-Za\-z0\-9./]. For example, "%.2s"
484 provides a two character salt and "$1$%.8s" tells some
485 versions of crypt(3) to use an MD5 algorithm and provides
486 8 random characters of salt. The default is "%s", which
487 provides 31 characters of salt.
489 .B pidfile <filename>
490 The ( absolute ) name of a file that will hold the
492 server's process ID ( see
494 ) if started without the debugging command line option.
497 Specify the referral to pass back when
499 cannot find a local database to handle a request.
500 If specified multiple times, each url is provided.
502 .B require <conditions>
503 Specify a set of conditions (separated by white space) to
504 require (default none).
505 The directive may be specified globally and/or per-database.
507 requires bind operation prior to directory operations.
509 requires session to be using LDAP version 3.
511 requires authentication prior to directory operations.
513 requires SASL authentication prior to directory operations.
515 requires strong authentication prior to directory operations.
516 The strong keyword allows protected "simple" authentication
517 as well as SASL authentication.
519 may be used to require no conditions (useful for clearly globally
520 set conditions within a particular database).
522 .B reverse-lookup on | off
523 Enable/disable client name reverse lookup (default is
525 if compiled with --enable-rlookups).
528 Specify the name of an LDIF(5) file containing user defined attributes
529 for the root DSE. These attributes are returned in addition to the
530 attributes normally produced by slapd.
532 .B sasl-authz-policy <policy>
533 Used to specify which rules to use for SASL Proxy Authorization. Proxy
534 authorization allows a client to authenticate to the server using one
535 user's credentials, but specify a different identity to use for authorization
536 and access control purposes. It essentially allows user A to login as user
537 B, using user A's password.
540 flag disables proxy authorization. This is the default setting.
543 flag will use rules in the
545 attribute of the authorization DN.
548 flag will use rules in the
550 attribute of the authentication DN.
553 flag will allow both of the above. The rules are simply regular expressions
554 specifying which DNs are allowed to perform proxy authorization. The
556 attribute in an entry specifies which other users
557 are allowed to proxy login to this entry. The
560 an entry specifies which other users this user can authorize as. Use of
563 abused if users are allowed to write arbitrary values to this attribute.
566 attribute must be protected with ACLs such that
567 only privileged users can modify it.
570 Used to specify the fully qualified domain name used for SASL processing.
572 .B sasl-realm <realm>
573 Specify SASL realm. Default is empty.
575 .B sasl-regexp <match> <replace>
576 Used by the SASL authorization mechanism to convert a SASL authenticated
577 username to an LDAP DN. When an authorization request is received, the SASL
581 are taken, when available, and combined into a SASL name of the
586 .B uid=<username>[,cn=<realm>],cn=<mechanism>,cn=auth
589 This SASL name is then compared against the
591 regular expression, and if the match is successful, the SASL name is
594 string. If there are wildcard strings in the
596 regular expression that are enclosed in parenthesis, e.g.
604 then the portion of the SASL name that matched the wildcard will be stored
605 in the numbered placeholder variable $1. If there are other wildcard strings
606 in parenthesis, the matching strings will be in $2, $3, etc. up to $9. The
607 placeholders can then be used in the
613 .B cn=$1,ou=Accounts,dc=$2,dc=$4.
617 The replaced SASL name can be either a DN or an LDAP URI. If the latter, the slapd
618 server will use the URI to search its own database, and if the search returns
619 exactly one entry, the SASL name is replaced by the DN of that entry.
622 options can be given in the configuration file to allow for multiple matching
623 and replacement patterns. The matching patterns are checked in the order they
624 appear in the file, stopping at the first successful match.
627 .\"Because the plus sign + is a character recognized by the regular expression engine,
628 .\"and it will appear in SASL names that include a REALM, be careful to escape the
629 .\"plus sign with a backslash \\+ to remove the character's special meaning.
632 .B sasl-secprops <properties>
633 Used to specify Cyrus SASL security properties.
636 flag (without any other properities) causes the flag properites
637 default, "noanonymous,noplain", to be cleared.
640 flag disables mechanisms susceptible to simple passive attacks.
643 flag disables mechanisms susceptible to active attacks.
646 flag disables mechanisms susceptible to passive dictionary attacks.
649 flag disables mechanisms which support anonymous login.
652 flag require forward secrecy between sessions.
655 require mechanisms which pass client credentials (and allow
656 mechanisms which can pass credentials to do so).
659 property specifies the minimum acceptable
660 .I security strength factor
661 as an integer approximate to effective key length used for
662 encryption. 0 (zero) implies no protection, 1 implies integrity
663 protection only, 56 allows DES or other weak ciphers, 112
664 allows triple DES and other strong ciphers, 128 allows RC4,
665 Blowfish and other modern strong ciphers. The default is 0.
668 property specifies the maximum acceptable
669 .I security strength factor
670 as an integer (see minssf description). The default is INT_MAX.
673 property specifies the maximum security layer receive buffer
674 size allowed. 0 disables security layers. The default is 65536.
677 Specify the distinguished name for the subschema subentry that
678 controls the entries on this server. The default is "cn=Subschema".
680 .B security <factors>
681 Specify a set of factors (separated by white space) to require.
682 An integer value is associated with each factor and is roughly
683 equivalent of the encryption key length to require. A value
684 of 112 is equivalent to 3DES, 128 to Blowfish, etc..
685 The directive may be specified globally and/or per-database.
687 specifies the overall security strength factor.
689 specifies the transport security strength factor.
691 specifies the TLS security strength factor.
693 specifies the SASL security strength factor.
695 specifies the overall security strength factor to require for
697 .B update_transport=<n>
698 specifies the transport security strength factor to require for
701 specifies the TLS security strength factor to require for
704 specifies the SASL security strength factor to require for
707 specifies the security strength factor required for
709 username/password authentication.
712 factor is measure of security provided by the underlying transport,
713 e.g. ldapi:// (and eventually IPSEC). It is not normally used.
715 .B sizelimit <integer>
717 .B sizelimit size[.{soft|hard|unchecked}]=<integer> [...]
718 Specify the maximum number of entries to return from a search operation.
719 The default size limit is 500.
720 The second format allows a fine grain setting of the size limits.
721 Extra args can be added on the same line.
724 for an explanation of the different flags.
726 .B sockbuf_max_incoming <integer>
727 Specify the maximum incoming LDAP PDU size for anonymous sessions.
728 The default is 262143.
730 .B sockbuf_max_incoming_auth <integer>
731 Specify the maximum incoming LDAP PDU size for authenticated sessions.
732 The default is 4194303.
735 Specify the srvtab file in which the kerberos keys necessary for
736 authenticating clients using kerberos can be found. This option is only
737 meaningful if you are using Kerberos authentication.
740 Specify the maximum size of the primary thread pool.
743 .B timelimit <integer>
745 .B timelimit time[.{soft|hard}]=<integer> [...]
746 Specify the maximum number of seconds (in real time)
748 will spend answering a search request. The default time limit is 3600.
749 The second format allows a fine grain setting of the time limits.
750 Extra args can be added on the same line.
753 for an explanation of the different flags.
755 .B ucdata-path <path>
756 Specify the path to the directory containing the Unicode character
757 tables. The default path is LOCALSTATEDIR/ucdata.
761 is built with support for Transport Layer Security, there are more options
764 .B TLSCipherSuite <cipher-suite-spec>
765 Permits configuring what ciphers will be accepted and the preference order.
766 <cipher-suite-spec> should be a cipher specification for OpenSSL. Example:
768 TLSCipherSuite HIGH:MEDIUM:+SSLv2
770 To check what ciphers a given spec selects, use:
772 openssl ciphers -v <cipher-suite-spec>
774 .B TLSCACertificateFile <filename>
775 Specifies the file that contains certificates for all of the Certificate
780 .B TLSCACertificatePath <path>
781 Specifies the path of a directory that contains Certificate Authority
782 certificates in separate individual files. Usually only one of this
783 or the TLSCACertificateFile is used.
785 .B TLSCertificateFile <filename>
786 Specifies the file that contains the
790 .B TLSCertificateKeyFile <filename>
791 Specifies the file that contains the
793 server private key that matches the certificate stored in the
794 .B TLSCertificateFile
795 file. Currently, the private key must not be protected with a password, so
796 it is of critical importance that it is protected carefully.
798 .B TLSRandFile <filename>
799 Specifies the file to obtain random bits from when /dev/[u]random
800 is not available. Generally set to the name of the EGD/PRNGD socket.
801 The environment variable RANDFILE can also be used to specify the filename.
803 .B TLSVerifyClient <level>
804 Specifies what checks to perform on client certificates in an
805 incoming TLS session, if any.
808 can be specified as one of the following keywords:
814 will not ask the client for a certificate.
817 The client certificate is requested. If no certificate is provided,
818 the session proceeds normally. If a bad certificate is provided,
819 it will be ignored and the session proceeds normally.
822 The client certificate is requested. If no certificate is provided,
823 the session proceeds normally. If a bad certificate is provided,
824 the session is immediately terminated.
826 .B demand | hard | true
827 These keywords are all equivalent, for compatibility reasons.
828 The client certificate is requested. If no certificate is provided,
829 or a bad certificate is provided, the session is immediately terminated.
831 Note that a valid client certificate is required in order to use the
832 SASL EXTERNAL authentication mechanism with a TLS session. As such,
835 setting must be chosen to enable SASL EXTERNAL authentication.
837 .SH GENERAL BACKEND OPTIONS
838 Options in this section only apply to the configuration file section
839 for the specified backend. They are supported by every
842 .B backend <databasetype>
843 Mark the beginning of a backend definition. <databasetype>
858 depending on which backend will serve the database.
860 .SH GENERAL DATABASE OPTIONS
861 Options in this section only apply to the configuration file section
862 for the database in which they are defined. They are supported by every
863 type of backend. Note that the
867 option are mandatory for each database.
869 .B database <databasetype>
870 Mark the beginning of a new database instance definition. <databasetype>
885 depending on which backend will serve the database.
890 will automatically maintain the
891 modifiersName, modifyTimestamp, creatorsName, and
892 createTimestamp attributes for entries. By default, lastmod is on.
894 .B maxderefdepth <depth>
895 Specifies the maximum number of aliases to dereference when trying to
896 resolve an entry, used to avoid inifinite alias loops. The default is 1.
899 This option puts the database into "read-only" mode. Any attempts to
900 modify the database will return an "unwilling to perform" error. By
901 default, readonly is off.
903 .B replica host=<hostname>[:port] [tls=yes|critical]
904 .B [suffix=<suffix> [...]]
905 .B bindmethod=simple|sasl [binddn=<simple DN>] [credentials=<simple password>]
906 .B [saslmech=<SASL mech>] [secprops=<properties>] [realm=<realm>]
907 .B [authcId=<authentication ID>] [authzId=<authorization ID>]
908 .B [attr[!]=<attr list>]
910 Specify a replication site for this database. Refer to the "OpenLDAP
911 Administrator's Guide" for detailed information on setting up a replicated
913 directory service. Zero or more
915 instances can be used to select the subtrees that will be replicated
916 (defaults to all the database). A
924 and should only be used when adequate security services
925 (e.g TLS or IPSEC) are in place. A
931 Specific security properties (as with the
933 keyword above) for a SASL bind can be set with the
935 option. A non-default SASL realm can be set with the
940 will use Kerberos, a kerberos instance should be given in
944 can be given after the
946 keyword to allow the selective replication of the listed attributes only;
949 mark is used, the list is considered exclusive, i.e. the listed attributes
951 If an objectClass is listed, all the related attributes
952 are (are not) replicated.
955 .B replogfile <filename>
956 Specify the name of the replication log file to log changes to.
957 The replication log is typically written by
963 for more information. The specified file should be located
964 in a directory with limited read/write/execute access as the replication
965 logs may contain sensitive information.
968 Specify the distinguished name that is not subject to access control
969 or administrative limit restrictions for operations on this database.
970 This DN may or may not be associated with an entry. An empty root
971 DN (the default) specifies no root access is to be granted. It is
972 recommended that the rootdn only be specified when needed (such as
973 when initially populating a database). If the rootdn is within
974 a namingContext (suffix) of the database, a simple bind password
975 may also be provided using the
980 Specify a password (or hash of the password) for the rootdn. The
981 password can only be set if the rootdn is within the namingContext
982 (suffix) of the database.
983 This option accepts all RFC 2307 userPassword formats known to
986 desription) as well as cleartext.
988 may be used to generate a hash of a password. Cleartext
989 and \fB{CRYPT}\fP passwords are not recommended. If empty
990 (the default), authentication of the root DN is by other means
991 (e.g. SASL). Use of SASL is encouraged.
993 .B suffix <dn suffix>
994 Specify the DN suffix of queries that will be passed to this
995 backend database. Multiple suffix lines can be given and at least one is
996 required for each database definition.
997 If the suffix of one database is "inside" that of another, the database
998 with the inner suffix must come first in the configuration file.
1000 .B suffixalias <alias> <aliased suffix>
1001 Specify an alternate suffix that may be used to reference an already defined
1002 database suffix. Operations specifying DNs residing under the alias
1003 will execute as if they had specified the aliased suffix.
1006 Specify that the current backend database is a subordinate of another
1007 backend database. A subordinate database may have only one suffix. This
1008 option may be used to glue multiple databases into a single namingContext.
1009 If the suffix of the current database is within the namingContext of a
1010 superior database, searches against the superior database will be
1011 propagated to the subordinate as well. All of the databases
1012 associated with a single namingContext should have identical rootdns.
1013 Behavior of other LDAP operations is unaffected by this setting. In
1014 particular, it is not possible to use moddn to move an entry from
1015 one subordinate to another subordinate within the namingContext.
1018 This option is only applicable in a slave
1020 It specifies the DN allowed to make changes to the replica (typically,
1023 binds as when making changes to the replica).
1026 Specify the referral to pass back when
1028 is asked to modify a replicated local database.
1029 If specified multiple times, each url is provided.
1030 .SH DATABASE-SPECIFIC OPTIONS
1031 Each database may allow specific configuration options; they are
1032 documented separately in the
1033 .BR slapd-<backend> (5)
1037 Here is a short example of a configuration file:
1041 include SYSCONFDIR/schema/core.schema
1042 pidfile LOCALSTATEDIR/slapd.pid
1045 suffix "dc=our-domain,dc=com"
1046 # The database directory MUST exist prior to
1047 # running slapd AND should only be accessible
1048 # by the slapd/tools. Mode 700 recommended.
1049 directory LOCALSTATEDIR/openldap-data
1050 # Indices to maintain
1051 index objectClass eq
1052 index cn,sn,mail pres,eq,approx,sub
1054 # We serve small clients that do not handle referrals,
1055 # so handle remote lookups on their behalf.
1058 uri ldap://ldap.some-server.com/
1063 "OpenLDAP Administrator's Guide" contains a longer annotated
1064 example of a configuration file.
1065 The original ETCDIR/slapd.conf is another example.
1069 default slapd configuration file
1073 .BR slapd-dnssrv (5),
1078 .BR slapd-passwd (5),
1080 .BR slapd-shell (5),
1083 .BR slapd.replog (5),
1084 .BR slapd.access (5),
1090 .BR slappassword (8),
1093 "OpenLDAP Administrator's Guide" (http://www.OpenLDAP.org/doc/admin/)
1094 .SH ACKNOWLEDGEMENTS
1096 is developed and maintained by The OpenLDAP Project (http://www.openldap.org/).
1098 is derived from University of Michigan LDAP 3.3 Release.