[Date Prev][Date Next]
Re: postalAddress matching rule
- To: firstname.lastname@example.org
- Subject: Re: postalAddress matching rule
- From: "Brett @Google" <email@example.com>
- Date: Fri, 5 Sep 2008 23:14:11 +1000
- Content-disposition: inline
- In-reply-to: <48BA80FD.firstname.lastname@example.org>
- References: <email@example.com> <48B43941.firstname.lastname@example.org> <email@example.com> <48B90CC6.firstname.lastname@example.org> <email@example.com> <48BA80FD.firstname.lastname@example.org>
On Sun, Aug 31, 2008 at 9:31 PM, Michael Ströder <email@example.com> wrote:
>>> slapo-collect should intercept the write request and forbid the write access
>>> if the attribute type is declared with COLLECTIVE.
>> Yep. That sounds reasonable, but i presume it should either return an
>> unwilling to perform, or silently ignore it.
> I'd prefer to not silently ignore it since returning unwillingToPerform
> clearly indicates that a client is misbehaving which needs correction.
OK, i've implemented collect_modify() which returns unwillingToPerform for any
modify operation which contains an attribute which is a collect
alone non-collectinfo objects including the parent object
the collect attributes are not dumped by slapcat, so no changes there