IMHO It would be "Slingy" if this was done inside the ResourceProvider.
Perhaps there needs to be a generic path-based ACL service which non-JCR ResourceProviders can tap into. Justin On 9/10/10 3:07 PM, Eric Norman wrote: > Perhaps we could just create a filter that does simple 'role' based access > checking. > > The filter could have a configuable map between resource path patterns and > the groupId the user must be a member of to read the resource. > > The launchpad could pre-create some well known goups and provide the default > mappings for the filter. > > WDYT? > > Regards, eric > > On Sep 10, 2010 11:29 AM, "Mike Moulton" <m...@meltmedia.com> wrote: > > I can create patches then to prevent anon access. What do you think about > tying the authorization to existing JCR ACL's like jcr:readAccessControl or > jcr:modifyAccessControl? If there is interest, I can include this in my > patches. > > -- Mike > > > > On Sep 9, 2010, at 5:07 PM, Justin Edelson wrote: > >> I can't speak to whether this was by intent o... >
