[
https://issues.apache.org/jira/browse/SLING-7960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16633795#comment-16633795
]
Bertrand Delacretaz commented on SLING-7960:
--------------------------------------------
Thank you very much for your patch - this was a bug indeed, as the syntax
differentiates between service users and regular users for deletions.
The corrected behavior won't be fully backwards compatible, as DELETE USER
previously also deleted service users but won't do that anymore.
Do you see this as a problem in the field and do you have suggestions (besides
release notes) on how to best avoid surprises when users switch to the fixed
{{jcr.repoinit}} module?
Maybe log a WARN message if a DELETE USER statement points to a service user
that would previously have been deleted?
> Repoinit: "delete user" also deletes service user
> -------------------------------------------------
>
> Key: SLING-7960
> URL: https://issues.apache.org/jira/browse/SLING-7960
> Project: Sling
> Issue Type: Bug
> Components: Repoinit
> Affects Versions: Repoinit JCR 1.1.8
> Reporter: Jörg Hoh
> Priority: Major
> Attachments: SLING-7960-2.patch, SLING-7960.patch
>
>
> My current application uses a regular user, but with some changes to the
> framework we need to migrate to regular service users. The service user is
> being added as part of the deployment.
> To automate this I decided to use the repoinit to remove the regular user and
> then deploy the service user. Which works fine, but only until the next time
> the repoinit is executed again. Because then the repoinit statement
> {{delete user foo}}
> purges the newly created serviceuser "foo". Which is totally unexpected,
> because there is a dedicated command "delete service user" which is supposed
> to remove users. So "delete user foo" must only delete a regular user "foo"
> but not a service user named "foo".
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
