[
https://issues.apache.org/jira/browse/SLING-3435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13937959#comment-13937959
]
Marius Petria commented on SLING-3435:
--------------------------------------
Hi,
It must have been something wrong in my local repo. The tests work fine with a
full clean build.
Regarding the connection between gates and providers, this works because no
path is treated as (.*) so the gates are registered for the whole resource
space.
It would be nice to also test access to providers for which no gate is matched
(that was the intent of /providers/unsecured/...). So, maybe we should just
define inline the gates to match /providers/secured(.*)
> ResourceAccessSecurity does not secure access for update operations
> -------------------------------------------------------------------
>
> Key: SLING-3435
> URL: https://issues.apache.org/jira/browse/SLING-3435
> Project: Sling
> Issue Type: New Feature
> Components: ResourceResolver
> Reporter: Marius Petria
> Assignee: Mike Müller
> Attachments: SLING-3435.1.patch, SLING-3435.2.patch, SLING-3435.patch
>
>
> ResourceAccessSecurity should use gates registered for update operations in
> order to secure access to modifiable value maps.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
