>>> Quanah Gibson-Mount <[email protected]> schrieb am 29.08.2019 um 15:41 in Nachricht <2B407C076711C27AEF9EBD7E@[192.168.1.144]>:
> > --On Thursday, August 29, 2019 9:32 AM +0200 Ulrich Windl > <[email protected]> wrote: > >>> I've seen this when an attribute is introduced into the cn=config >>> database that's not part of the built‑in slapd schema. It can be >>> harmless in that case. >> >> I grepped for the attribute in external schema files, but didn't find it. >> As I found it when querying slapd, I conclude that the definition shown >> above must be build into slapd. > > Using the power of the source, auditcontext is defined in the > slapo-accesslog overlay. Right, found it there: ( 1.3.6.1.4.1.4203.666.11.5.1.30 NAME 'auditContext' DESC 'DN of auditContainer' SYNTAX 1.3.6.1.4.1.1466.115.121.1.12 SINGLE-VALUE NO-USER-MODIFICATION USAGE dSAOperation ) But I did not find an object definition that uses that attribute (any more). At least not in that module. My guess is that "auditContext: cn=audit" was valid some time in the past, but isn't any more. Still cn=audit continues to work as base DN. Late response, sorry. Regards, Ulrich > > --Quanah > > > -- > > Quanah Gibson-Mount > Product Architect > Symas Corporation > Packaged, certified, and supported LDAP solutions powered by OpenLDAP: > <http://www.symas.com>
