1 .TH SLAPO-ACCESSLOG 5 "RELEASEDATE" "OpenLDAP LDVERSION"
2 .\" Copyright 2005 The OpenLDAP Foundation All Rights Reserved.
3 .\" Copying restrictions apply. See COPYRIGHT/LICENSE.
6 slapo-accesslog \- Access Logging overlay
10 The Access Logging overlay can be used to record all accesses to a given
11 backend database on another database. This allows all of the activity on
12 a given database to be reviewed using arbitrary LDAP queries, instead of
13 just logging to local flat text files. Configuration options are available
14 for selecting a subset of operation types to log, and to automatically
15 prune older log records from the logging database. Log records are stored
16 with a custom schema to assure their readability whether viewed as LDIF
21 options apply to the Access Logging overlay.
22 They should appear after the
24 directive and before any subsequent
29 Specify the suffix of a database to be used for storing the log records.
30 The specified database must have already been configured in a prior section
31 of the config file. The suffix entry of the database must also already
32 exist. The log entries will be generated as the immediate children of the
35 .B logops <operations>
36 Specify which types of operations to log. The valid operation types are
37 abandon, add, bind, compare, delete, extended, modify, modrdn, search,
38 and unbind. Aliases for common sets of operations are also available:
42 add, delete, modify, modrdn
54 .B logpurge <age> <interval>
55 Specify the maximum age for log entries to be retained in the database,
56 and how often to scan the database for old entries. Both the
60 are specified as a time span in days, hours, minutes, and seconds. The
61 time format is [dd+]hh:mm[:ss] i.e., the days and seconds components are
62 optional but hours and minutes are required. Each numeric field must be
63 exactly two digits. For example
68 logpurge 02+00:00 01+00:00
71 would specify that the log database should be scanned every day for old
72 entries, and entries older than two days should be deleted. When using a
73 log database that supports ordered indexing on generalizedTime attributes,
74 specifying an eq index on the
76 attribute will greatly benefit the performance of the purge operation.
87 suffix dc=example,dc=com
97 overlay defines a number of object classes for use in the logs. There is
100 class from which two additional classes,
104 are derived. Object classes for each type of LDAP operation are further
105 derived from these classes. This object class hierarchy is designed to
106 allow flexible yet efficient searches of the log based on either a specific
107 operation type's class, or on more general classifications. The definition
113 ( 1.3.6.1.4.1.4203.666.11.5.2.1
115 DESC 'OpenLDAP request auditing'
117 MUST ( reqStart $ reqType $ reqSession )
118 MAY ( reqDN $ reqAuthzID $ reqControls $ reqRespControls $
119 reqEnd $ reqResult $ reqMessage ) )
122 Note that all of the OIDs used in the logging schema currently reside
123 under the OpenLDAP Experimental branch. It is anticipated that thay
124 will migrate to a Standard branch in the future.
126 An overview of the attributes follows:
130 provide the start and end time of the operation, respectively. They use
131 generalizedTime syntax. The
133 attribute is also used as the RDN for each log entry.
137 attribute is a simple string containing the type of operation
142 etc. For extended operations, the type also includes the OID of the
143 extended operation, e.g.
144 .B extended(1.2.3.4.1)
148 attribute is an implementation-specific identifier that is common to
149 all the operations associated with the same LDAP session. Currently this
150 is slapd's internal connection ID, stored in decimal.
154 attribute is the distinguishedName of the target of the operation. E.g., for
155 a Bind request, this is the Bind DN. For an Add request, this is the DN
156 of the entry being added. For a Search request, this is the base DN of
161 attribute is the distinguishedName of the user that performed the operation.
162 This will usually be the same name as was established at the start of a
163 session by a Bind request (if any) but may be altered in various
169 attributes carry any controls sent by the client on the request and returned
170 by the server in the response, respectively. The attribute values are just
171 uninterpreted octet strings.
175 attribute is the numeric LDAP result code of the operation, indicating
176 either success or a particular LDAP error code. An error code may be
177 accompanied by a text error message which will be recorded in the
181 Operation-specific classes are defined with additional attributes to carry
182 all of the relevant parameters associated with the operation:
186 ( 1.3.6.1.4.1.4203.666.11.5.2.4
188 DESC 'Abandon operation'
189 SUP auditObject STRUCTURAL
197 attribute contains the message ID of the request that was abandoned.
201 ( 1.3.6.1.4.1.4203.666.11.5.2.5
204 SUP auditWriteObject STRUCTURAL
210 class inherits from the
212 class. The Add and Modify classes are essentially the same. The
214 attribute carries all of the attributes of the original entry being added.
215 (Or in the case of a Modify operation, all of the modifications being
216 performed.) The values are formatted as
221 attribute:<+|-|=|#> [ value]
224 Where '+' indicates an Add of a value, '-' for Delete, '=' for Replace,
225 and '#' for Increment. In an Add operation, all of the reqMod values will
226 have the '+' designator.
232 ( 1.3.6.1.4.1.4203.666.11.5.2.6
234 DESC 'Bind operation'
235 SUP auditObject STRUCTURAL
243 attribute which contains the Bind Method used in the Bind. This will be
246 for LDAP Simple Binds or
249 Note that unless configured as a global overlay, only Simple Binds using
250 DNs that reside in the current database will be logged.
254 ( 1.3.6.1.4.1.4203.666.11.5.2.7
256 DESC 'Compare operation'
257 SUP auditObject STRUCTURAL
265 attribute carries the Attribute Value Assertion used in the compare request.
269 ( 1.3.6.1.4.1.4203.666.11.5.2.8
271 DESC 'Modify operation'
272 SUP auditWriteObject STRUCTURAL
278 operation has already been described.
282 ( 1.3.6.1.4.1.4203.666.11.5.2.9
284 DESC 'ModRDN operation'
285 SUP auditWriteObject STRUCTURAL
286 MUST ( reqNewRDN $ reqDeleteOldRDN )
294 attribute to carry the new RDN of the request.
297 attribute is a Boolean value showing
299 if the old RDN was deleted from the entry, or
301 if the old RDN was preserved.
304 attribute carries the DN of the new parent entry if the request specified
309 ( 1.3.6.1.4.1.4203.666.11.5.2.10
311 DESC 'Search operation'
312 SUP auditReadObject STRUCTURAL
313 MUST ( reqScope $ reqAttrsOnly )
314 MAY ( reqFilter $ reqAttr $ reqEntries $ reqSizeLimit $
322 attribute contains the scope of the original search request, i.e.
330 attribute is a Boolean value showing
332 if only attribute names were requested, or
334 if attributes and their values were requested.
337 attribute carries the filter used in the search request.
340 attribute lists the requested attributes if specific attributes were
344 attribute is the integer count of how many entries were returned by
350 attributes indicate what limits were requested on the search operation.
354 ( 1.3.6.1.4.1.4203.666.11.5.2.11
356 DESC 'Extended operation'
357 SUP auditObject STRUCTURAL
363 class represents an LDAP Extended Operation. As noted above, the actual OID of
364 the operation is included in the
366 attribute of the parent class. If any optional data was provided with the
367 request, it will be contained in the
369 attribute as an uninterpreted octet string.
372 The Access Log implemented by this overlay may be used for a variety of
373 other tasks, e.g. as a ChangeLog for a replication mechanism, as well
374 as for security/audit logging purposes.
379 default slapd configuration file
385 This module was written in 2005 by Howard Chu of Symas Corporation.