You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Marius Petria (JIRA)" <ji...@apache.org> on 2014/03/18 14:11:43 UTC

[jira] [Updated] (SLING-3458) Restrictions imposed by ProviderResourceAccessSecurity should not be discarded by ApplicationResourceAccessSecurity

     [ https://issues.apache.org/jira/browse/SLING-3458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marius Petria updated SLING-3458:
---------------------------------

    Attachment: SLING-3458.patch

I have updated the ResourceResolver to use the value returned by the ProviderResourceAccessSecurity service when evaluating the restrictions imposed by ApplicationResourceAccessSecurity.

I have also updated the corresponding integration test to reflect the correct behavior.

> Restrictions imposed by ProviderResourceAccessSecurity should not be discarded by ApplicationResourceAccessSecurity
> -------------------------------------------------------------------------------------------------------------------
>
>                 Key: SLING-3458
>                 URL: https://issues.apache.org/jira/browse/SLING-3458
>             Project: Sling
>          Issue Type: Bug
>          Components: ResourceResolver
>            Reporter: Marius Petria
>         Attachments: SLING-3458.patch
>
>
> Restrictions imposed by ProviderResourceAccessSecurity should not be discarded by ApplicationResourceAccessSecurity.
> More specifically if ProviderResourceAccessSecurity wrapps the original resource to protect it against modification then any additional transformations made by ApplicationResourceAccessSecurity should use the wrapped resource.



--
This message was sent by Atlassian JIRA
(v6.2#6252)