You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Bertrand Delacretaz (JIRA)" <ji...@apache.org> on 2016/07/15 09:25:20 UTC
[jira] [Commented] (SLING-5848) Define service user and ACLs for
Scripting
[ https://issues.apache.org/jira/browse/SLING-5848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15379094#comment-15379094 ]
Bertrand Delacretaz commented on SLING-5848:
--------------------------------------------
If we start creating service users that Sling needs I'm in favor of using a {{sling-}} prefix for them.
> 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}} (?)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)