[
https://issues.apache.org/jira/browse/SLING-2698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13610052#comment-13610052
]
Mike Müller commented on SLING-2698:
------------------------------------
Unfortunately nobody has answered/commented on my related thread [1].
The idea is, to make it very easy to apply resource access security on resource
providers which do not have any underlaying ACLs. If we do that it's just a
logical consequence that either ResourceAccessSecurity or ResourceAccessGate
should be somewhere in the API.
I think it all boils down to the question if we want to make Sling a frontend
for whatever resources and not only for resources from a JCR. And I really hope
that we are going in this direction, because this would open a huge bunch of
possibilities to use Sling in the future - and is a big chance to increase the
user (and hopefully also the developer) base of Sling.
[1] http://sling.markmail.org/thread/4nb76qklvjfxl3z2
> resource access security service for resource providers without backing ACLs
> ----------------------------------------------------------------------------
>
> Key: SLING-2698
> URL: https://issues.apache.org/jira/browse/SLING-2698
> Project: Sling
> Issue Type: New Feature
> Components: ResourceResolver
> Reporter: Mike Müller
> Assignee: Mike Müller
> Fix For: Resource Resolver 1.1.0
>
> Attachments: resource-resolver-wrapper.patch
>
>
> Adding a minmal resource access gate as discussed in [1].
> First step is to define the API interface and a minimal implementation which
> allows to define READ access (rest of CRUD can follow later)
> [1] http://markmail.org/thread/4ctczoiy533tquyl
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
