[
https://issues.apache.org/jira/browse/SLING-2698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13610075#comment-13610075
]
Bertrand Delacretaz commented on SLING-2698:
--------------------------------------------
I agree with Alex about having those new APIs in a separate bundle,
resource-security-api or rsec-api maybe. That will be a very small bundle
initially but that doesn't matter IMO - a bundle should do one thing and one
thing well.
A separate API bundle makes it much easier to differentiate between the "all
JCR" and "non-JCR" use cases of Sling, which IMO is important and helps address
the concerns expressed by Angela and Lars K about not blurring the JCR security
picture.
> 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
