[
https://issues.apache.org/jira/browse/SLING-5848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15399019#comment-15399019
]
Oliver Lietz commented on SLING-5848:
-------------------------------------
[~anchela], thanks for your answer. Much appreciated!
We *have* to care about the format of the node name to not interfere with
Sling's resource resolution. If the name contains dots ({{sling.scripting}}) it
could clash with selectors and extensions. If the name gets randomized we are
save.
* http://localhost:8181/home/users/system/sling-scripting.json (/)
* http://localhost:8181/home/users/system/sling.scripting.json (!)
* http://localhost:8181/home/users/system/sB-CSiB-KD0S0ROF6hLtICN30xQvU5rq.json
(/)
> 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)
