1SLAPD.BACKENDS(5) File Formats Manual SLAPD.BACKENDS(5)
2
3
4
6 slapd.backends - backends for slapd, the stand-alone LDAP daemon
7
9 The slapd(8) daemon can use a variety of different backends for serving
10 LDAP requests. Backends may be compiled statically into slapd, or when
11 module support is enabled, they may be dynamically loaded. Multiple in‐
12 stances of a backend can be configured, to serve separate databases
13 from the same slapd server.
14
15
16 Configuration options for each backend are documented separately in the
17 corresponding slapd-<backend>[22m(5) manual pages.
18
19 asyncmeta
20 This backend performs basic LDAP proxying with respect to a set
21 of remote LDAP servers. It is an enhancement of the ldap backend
22 that operates asynchronously, to prevent tying up slapd threads
23 while waiting for operations to complete.
24
25 config This backend is used to manage the configuration of slapd at
26 run-time. Unlike other backends, only a single instance of the
27 config backend may be defined. It also instantiates itself auto‐
28 matically, so it is always present even if not explicitly de‐
29 fined in the slapd.conf(5) file.
30
31 dnssrv This backend is experimental. It serves up referrals based upon
32 SRV resource records held in the Domain Name System.
33
34 ldap This backend acts as a proxy to forward incoming requests to an‐
35 other LDAP server.
36
37 ldif This database uses the filesystem to build the tree structure of
38 the database, using plain ascii files to store data. Its usage
39 should be limited to very simple databases, where performance is
40 not a requirement. This backend also supports subtree renames.
41
42 mdb This is the recommended primary backend. This backend uses
43 OpenLDAP's own MDB transactional database library. This backend
44 also supports subtree renames.
45
46 meta This backend performs basic LDAP proxying with respect to a set
47 of remote LDAP servers. It is an enhancement of the ldap back‐
48 end.
49
50 monitor
51 This backend provides information about the running status of
52 the slapd daemon. Only a single instance of the monitor backend
53 may be defined.
54
55 null Operations in this backend succeed but do nothing.
56
57 passwd This backend is provided for demonstration purposes only. It
58 serves up user account information from the system passwd(5)
59 file.
60
61 perl This backend embeds a perl(1) interpreter into slapd. It runs
62 Perl subroutines to implement LDAP operations. This backend is
63 deprecated.
64
65 relay This backend is experimental. It redirects LDAP operations to
66 another database in the same server, based on the naming context
67 of the request. Its use requires the rwm overlay (see
68 slapo-rwm(5) for details) to rewrite the naming context of the
69 request. It is primarily intended to implement virtual views on
70 databases that actually store data.
71
72 sql This backend is experimental and deprecated. It services LDAP
73 requests from an SQL database.
74
75 wiredtiger
76 This backend is experimental. It services LDAP requests from a
77 wiredtiger database.
78
80 /etc/openldap/slapd.conf
81 default slapd configuration file
82
83 /etc/openldap/slapd.d
84 default slapd configuration directory
85
87 ldap(3), slapd-asyncmeta(5), slapd-config(5), slapd-dnssrv(5),
88 slapd-ldap(5), slapd-ldif(5), slapd-mdb(5), slapd-meta(5), slapd-moni‐
89 tor(5), slapd-null(5), slapd-passwd(5), slapd-perl(5), slapd-relay(5),
90 slapd-sql(5), slapd-wt(5), slapd.conf(5), slapd.overlays(5), slapd(8).
91 "OpenLDAP Administrator's Guide" (http://www.OpenLDAP.org/doc/admin/)
92
94 OpenLDAP Software is developed and maintained by The OpenLDAP Project
95 <http://www.openldap.org/>. OpenLDAP Software is derived from the Uni‐
96 versity of Michigan LDAP 3.3 Release.
97
98
99
100OpenLDAP 2.6.6 2023/07/31 SLAPD.BACKENDS(5)