>> Quanah Gibson-Mount <quanah(a)symas.com> schrieb am
29.08.2019 um 15:41 in
--On Thursday, August 29, 2019 9:32 AM +0200 Ulrich Windl
>> 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
found it there:
( 126.96.36.199.4.1.4203.6188.8.131.52.30 NAME 'auditContext' DESC 'DN of
auditContainer' SYNTAX 184.108.40.206.4.1.14220.127.116.11.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.
Packaged, certified, and supported LDAP solutions powered by OpenLDAP: