Howard Chu hyc@symas.com schrieb am 22.07.2020 um 19:49 in Nachricht
dbfb1513-f1ef-d44e-a2f6-c5533a530884@symas.com:
Ulrich Windl wrote:
Quanah Gibson-Mount quanah@symas.com 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 Ulrich.Windl@rz.uni-regensburg.de 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).
It is clearly an operational attribute.
Now I see it, too ;-)
-- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/