[
https://issues.apache.org/jira/browse/SLING-6984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16132009#comment-16132009
]
Timothee Maret commented on SLING-6984:
---------------------------------------
Thanks [~bdelacretaz]!
The Jackrabbit API provides a single method to enable & disable a user [0]. The
implementation will enable the user if a {{null}} reason is passed and disable
the user if the reason is not {{null}}.
With the change in http://svn.apache.org/r1805165 the reason seems to be
optional. Is the intention to mimic the Jackrabbit API (enable/disable in the
same "method") or would we create two "methods", one for enabling and one for
disabling and make sure the enable method at least provide a string to the
Jackrabbit counterpart ?
>From the commit http://svn.apache.org/r1805165 I'd assume the latter but I may
>miss the intent.
[0]
https://github.com/apache/jackrabbit/blob/trunk/jackrabbit-api/src/main/java/org/apache/jackrabbit/api/security/user/User.java#L76-L86
> Allow to disable service user
> -----------------------------
>
> Key: SLING-6984
> URL: https://issues.apache.org/jira/browse/SLING-6984
> Project: Sling
> Issue Type: Improvement
> Components: Repoinit
> Affects Versions: Repoinit Parser 1.1.0, Repoinit JCR 1.1.4
> Reporter: Timothee Maret
> Assignee: Timothee Maret
>
> Currently the repoinit module does not support -removing- disabling service
> users.
> Disbling -Removing- service user is required when one user is no longer
> needed due to service user sharing among components.
> The syntax could be the one proposed by [~anchela]
> {code}
> disable service user <serviceUserId> <disableMessage>
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
