[
https://issues.apache.org/jira/browse/SLING-4269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu resolved SLING-4269.
------------------------------------
Resolution: Fixed
Fixed in https://svn.apache.org/r1648267
> SlingContextImpl's resource resolver should be an administrative one
> --------------------------------------------------------------------
>
> Key: SLING-4269
> URL: https://issues.apache.org/jira/browse/SLING-4269
> Project: Sling
> Issue Type: Bug
> Components: Testing
> Affects Versions: Testing Sling Mock 1.1.0
> Reporter: Robert Munteanu
> Assignee: Robert Munteanu
> Fix For: Testing Sling Mock 1.1.2
>
>
> The SlingContextImpl creates a resource resolver using
> {{resourceResolverFactory.getResourceResolver}}. The javadoc for this method
> specifies that:
> {quote}If the authenticationInfo map is null the ResourceResolver returned
> will generally not be authenticated and only provide minimal privileges, if
> any at all.{quote}
> This means that this resource resolver is very hard to use productively when
> using the JCR_JACKRABBIT resource resolver type with ACLs set. Therefore the
> resource resolver should be an admin one, with a guest being accessible using
> regular Sling/JCR APIs, e.g.
> {code}context.resourceResolver().adaptTo(Session.class).getRepository().login(new
> GuestCredentials());{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
