[
https://issues.apache.org/jira/browse/SLING-6466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15824154#comment-15824154
]
Carsten Ziegeler commented on SLING-6466:
-----------------------------------------
[~olli] I think keeping separate users is the better option as users can more
easily fine tune the access rights.
For the naming:
org.apache.sling.resourceresolver:read - this one is used for the web console
(actually it is not, but that is a bug), for reading the resource type
hierarchy and for the OSGi observation. That's why I simply named it "read" :)
Now, maybe it would be better to split this into three users and name them
appropriately?
> Rename system user sling-readall and sub service read
> -----------------------------------------------------
>
> Key: SLING-6466
> URL: https://issues.apache.org/jira/browse/SLING-6466
> Project: Sling
> Issue Type: Task
> Components: JCR, Karaf, Launchpad, ResourceResolver
> Reporter: Oliver Lietz
> Fix For: Resource Resolver 1.5.12, Launchpad Builder 9
>
>
> We already have several system users with {{read}} permissions on {{/}}, but
> every system user has a dedicated purpose and usually its purpose is clear
> from the name. {{sling-readall}} breaks this pattern and it should be
> adjusted.
> actual:
> {noformat}
> org.apache.sling.resourceresolver:mapping=sling-mapping
> org.apache.sling.resourceresolver:read=sling-readall
> org.apache.sling.jcr.resource:observation=sling-readall
> {noformat}
> recommended:
> {noformat}
> org.apache.sling.resourceresolver:mapping=sling-mapping
> org.apache.sling.resourceresolver:observation=sling-observation
> org.apache.sling.jcr.resource:observation=sling-observation
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
