You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2017/01/20 06:40:26 UTC

[jira] [Resolved] (SLING-6466) Rename sub service users

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

Carsten Ziegeler resolved SLING-6466.
-------------------------------------
    Resolution: Fixed

Changed the sub service name as suggested above in rev 1779570
Updated launchpad in rev 1779571

> Rename sub service users
> ------------------------
>
>                 Key: SLING-6466
>                 URL: https://issues.apache.org/jira/browse/SLING-6466
>             Project: Sling
>          Issue Type: Task
>          Components: Launchpad, ResourceResolver
>            Reporter: Oliver Lietz
>            Assignee: Carsten Ziegeler
>             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)