[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
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: hyc@symas.com
- Date: Mon, 15 Aug 2011 20:35:17 GMT
- Auto-submitted: auto-generated (OpenLDAP-ITS)
michael@stroeder.com wrote:
> Full_Name:
> Version: 2.4.26
> OS:
> URL: ftp://ftp.openldap.org/incoming/
> Submission from: (NULL) (84.163.26.156)
>
>
> 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.
--
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/