[
https://issues.apache.org/jira/browse/SLING-5848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15399106#comment-15399106
]
Oliver Lietz commented on SLING-5848:
-------------------------------------
Let me rephrase: The dots *may* lead to problems (\[1]) when someone queries
users by HTTP and wants to use selectors. The URL
http://localhost:8181/home/users/system/sling.scripting.json for service user
{{sling.scripting}} works and will give you the user node as JSON.
If we configure {{RandomAuthorizableNodeName}} in Sling Launchpad and use dots
for service user names in Sling Launchpad we are save. If anyone alters that
configuration it's up to him.
I'm in favor of a consistent pattern for user names – whether we use {{sling.}}
or {{sling-}} as prefix (see my comment above why {{sling.}} came to mind).
\[1] Assets in AEM DAM
> Define service user and ACLs for Scripting
> ------------------------------------------
>
> Key: SLING-5848
> URL: https://issues.apache.org/jira/browse/SLING-5848
> Project: Sling
> Issue Type: Task
> Components: Scripting
> Reporter: Oliver Lietz
>
> Scripting implementations require a (service) ResourceResolver with very
> limited read rights to read scripts.
> Reading can be limited to these paths:
> * {{/apps}}
> * {{/libs}}
> * {{/etc}} (?)
> Name for service user: {{scripting}} or {{sling-scripting}} or
> {{sling.scripting}} (?)
> *repoinit:*
> {noformat}
> create path /apps
> create path /libs
> create service user sling-scripting
> set ACL for sling-scripting
> allow jcr:read on /apps
> allow jcr:read on /libs
> end
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
