[Date Prev][Date Next]
Re: (ITS#7019) attribute auditContext should not get replicated
- To: openldap-its@OpenLDAP.org
- Subject: Re: (ITS#7019) attribute auditContext should not get replicated
- From: email@example.com
- Date: Mon, 15 Aug 2011 20:48:11 GMT
- Auto-submitted: auto-generated (OpenLDAP-ITS)
> firstname.lastname@example.org wrote:
>> Version: 2.4.26
>> URL: ftp://ftp.openldap.org/incoming/
>> Submission from: (NULL) (184.108.40.206)
>> It seems that attribute auditContext is replicated to consumers if there's an
>> accesslog DB configured at the provider. IMO this does not make sense since the
>> accesslog DB is not replicated and one might not want to load slapo-accesslog
>> module at all in the consumer's config.
>> In a 2-way MMR setup with accesslog DB attached to both master providers the
>> auditContext contains two values for auditContext and even the same one.
> Since a syncrepl operation is a regular LDAP search, the provider sends
> everything that matches the search request. Probably we should be filtering
> out DSA-specific opattrs at the consumer side.
Hm, I take this back. slapd/result.c already filters out DSA-specific opattrs
on the provider side, when the Syncrepl control is present. Something else is
going on here, but since you failed to provide any config info there's no way
to tell where the problem is.
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/