Mailing-List: contact oak-dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: oak-dev@jackrabbit.apache.org
Received-SPF: pass (athena.apache.org: domain of aklimets@adobe.com designates
 64.18.1.33 as permitted sender)
From: Alexander Klimetschek <aklimets@adobe.com>
To: "oak-dev@jackrabbit.apache.org" <oak-dev@jackrabbit.apache.org>
Date: Fri, 8 Nov 2013 20:44:14 +0000
Subject: Re: ACLs checked within observation events?
Thread-Topic: ACLs checked within observation events?
Thread-Index: Ac7cw0m7ZX2NI6U9QB6Pwg2hJfrWhw==
Message-ID: <83336513-56DF-4297-B624-8757CF5A89A4@adobe.com>
References: <CEA1014D.C840%anchela@adobe.com> <527CA2C3.7090403@apache.org>
In-Reply-To: <527CA2C3.7090403@apache.org>
Accept-Language: de-DE, en-US
Content-Language: en-US
acceptlanguage: de-DE, en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

On 08.11.2013, at 00:37, Michael D=FCrig <mduerig@apache.org> wrote:

> On 7.11.13 8:36 , Angela Schreiber wrote:
>> according to the latest information i got from michael
>> this is not yet implemented... but it's definitely planned
>=20
> Right, this is still to do. See TODO tags in the SecureValidator class.

Ok, I created https://issues.apache.org/jira/browse/OAK-1163 so it can be t=
racked.

> No, the SecureValidator class operates on non secured node states. My=20
> very first idea was to operate on secured node states but that wouldn't=20
> work for items whose parent is not accessible. It would not generate=20
> events for such items since diffing would stop at the (non accessible)=20
> parent even though there are more changes in the sub tree below that are=
=20
> accessible.

Makes sense.

Cheers,
Alex=