[
https://issues.apache.org/jira/browse/SLING-5355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joerg Hoh closed SLING-5355.
----------------------------
> Create service users and ACLs from the provisioning model
> ---------------------------------------------------------
>
> Key: SLING-5355
> URL: https://issues.apache.org/jira/browse/SLING-5355
> Project: Sling
> Issue Type: New Feature
> Components: Repoinit
> Reporter: Bertrand Delacretaz
> Assignee: Bertrand Delacretaz
> Priority: Major
> Fix For: Slingstart Maven Plugin 1.4.2, Repoinit Parser 1.0.2,
> Repoinit JCR 1.0.0
>
>
> As discussed in the "Removing loginAdministrative, how to test that, and
> service username conventions" thread on our dev list [1] we need to be able
> to create service users and set the corresponding ACLs from our provisioning
> model.
> This should be implemented using distinct utility classes, one for the users
> and one for the ACLs, that take simple mini-languages as input. This will
> allow for reusing these utilities in test code for example.
> [1] http://markmail.org/message/kcvuhwfdald2dyuz
> *Edit: high-level requirements*
> As discussed in the "SLING-5355 - configs vs. content for ACLs and service
> users" thread - http://markmail.org/message/tzno2via2wjckhuc
> * HR1 - Create service users and set their ACLs as defined in the Sling
> instance's provisioning model.
> * HR2 - Create initial paths like /var/discovery, so that ACLs can be set on
> them.
> * HR3 - Make the full text of the ACL definitions available at runtime for
> auditing purposes (see Michael Marth's Dec.17 comment in SLING-5355). Also
> useful for upgrades where merging with conflict detection is needed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
