<quote who="Pierangelo Masarati">
Gavin Henry wrote:
<quote who="Aaron Richton"> > In the spirit of starting with the obvious, do you find auditContext > under > cn=Subschema?
I'll check ;-)
But why would this attribute get into the normal data dir?
that attribute is added to the producer to provide a pointer to the database that contains the log. The attributeType itself is defined by slapo-accesslog(5), so the overlay should be present (but does not need to be instantiated; just compiled in or, if built as module, loaded) in the consumer in order to have that attribute defined.
Why would I need to load the accesslog overlay on the consumer? I never have before.
The only thing that mentions accesslog is the normal delta-syncrepl directives:
logbase="cn=accesslog" logfilter="(&(objectClass=auditWriteObject)(reqResult=0))" syncdata=accesslog
etc.
I'm confused here. Is it a 2.4 change?