[
https://issues.apache.org/jira/browse/SLING-2875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Müller updated SLING-2875:
-------------------------------
Attachment: SLING-2875.patch
I added a patch to introduce the new property and it's handling inside the
resource resolver bundle.
Maybe someone has a better alternative to the
SortedProviderList#getProviderHandler method. Because this SortedProviderList
does return only "plain" ResourceProvider instances the configuration hold in
ProviderHandler get's lost and has to be gained from the list for every
provider again...
> Easy way for enabling ResourceAccessSecurity for resource providers without
> underlaying ACLs
> --------------------------------------------------------------------------------------------
>
> Key: SLING-2875
> URL: https://issues.apache.org/jira/browse/SLING-2875
> Project: Sling
> Issue Type: New Feature
> Components: ResourceResolver
> Reporter: Mike Müller
> Assignee: Mike Müller
> Priority: Minor
> Attachments: SLING-2875.patch
>
>
> As discussed in SLING-2698 and on the mailing list:
> To enable ResourceAccessSecurity service for a specific provider we introduce
> a new service property for ResourceProvider services.
> The property is set to false by default and only resource providers without
> underlying ACLs should set this property to true.
--
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
