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

Posted to dev@sling.apache.org by "Tommaso Teofili (JIRA)" <ji...@apache.org> on 2014/10/14 17:09:43 UTC

[jira] [Resolved] (SLING-3899) Access content for replication on behalf of the user that triggered the replication

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

Tommaso Teofili resolved SLING-3899.
------------------------------------
    Resolution: Fixed

applied patch in r1631780, thanks Marius!

> Access content for replication on behalf of the user that triggered the replication
> -----------------------------------------------------------------------------------
>
>                 Key: SLING-3899
>                 URL: https://issues.apache.org/jira/browse/SLING-3899
>             Project: Sling
>          Issue Type: Improvement
>          Components: Replication
>            Reporter: Marius Petria
>            Assignee: Tommaso Teofili
>         Attachments: SLING-3899.diff
>
>
> Currently the content is accessed via an administrative session. We need to pass a ResourceResolver via all APIs to ensure that the content is accessed only be users that have the right.
> For rule triggered requests the actions should be done on the behalf of a replication-service-user.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)