[
https://issues.apache.org/jira/browse/OAK-7900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16686788#comment-16686788
]
Lars Krapf commented on OAK-7900:
---------------------------------
[~anchela]: Looks very good to me too, thanks.
> Allow to spot User.disable with a new, dedicated UserAction
> -----------------------------------------------------------
>
> Key: OAK-7900
> URL: https://issues.apache.org/jira/browse/OAK-7900
> Project: Jackrabbit Oak
> Issue Type: New Feature
> Components: security-spi
> Reporter: angela
> Assignee: angela
> Priority: Major
> Fix For: 1.10
>
> Attachments: OAK-7900.patch
>
>
> [~chaotic], as discussed off list we lack the ability to react to
> {{User.disable(String)}} with the current {{AuthorizableAction}} interface,
> while at the same time encouraging API consumers to disable users instead of
> removing them.
> One use case for such a method would be deleting additional information
> stored with the user account such as e.g. profile data, preferences, as soon
> as the user gets disabled.
> Since extending {{AuthorizableAction}} would require a major bump of the
> exported version, I would suggest to introduce a new {{UserAction}}
> interface, providing that new method, in correspondance to {{GroupAction}},
> which covers group specific actions. And, in an ideal world
> {{AuthorizableAction.onPasswordChange}} would also reside with {{UserAction}}.
> [~stillalex], wdyt?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
