[jira] [Commented] (OAK-5118) SynchronizationMBean: Deprecate syncAllUsers and syncAllExternalUsers

["Thomas März (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/OAK-5118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15676494#comment-15676494 ] 

Thomas März commented on OAK-5118:
----------------------------------

There are use-cases for these operations like having all external users available to assign groups before their first login. Of course there are other ways to achieve this, but all in all the process will be expensive in some way. It is not sensible to deprecate these methods just because how they are documented.

> SynchronizationMBean: Deprecate syncAllUsers and syncAllExternalUsers
> ---------------------------------------------------------------------
>
>                 Key: OAK-5118
>                 URL: https://issues.apache.org/jira/browse/OAK-5118
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: auth-external
>            Reporter: angela
>
> The following 2 methods defined by {{SyncronizationMBean}} have been introduced with a warning about being potentially expensive [0]:
> - {{syncAllUsers}}
> - {{syncAllExternalUsers}}
> To me defining API that is designed with scalability issues in mind, looks like a troublesome pattern. As far as I understood from the history associated with this, I assume that it was introduced to allow for upfront sync to workaround other issues faced by sync-upon-login.
> With the latest improvements and features introduced wrt to the user-sync, I think we should move forward deprecating the troublesome methods for the upcoming 1.6 release.
> [0] Quote from Javadoc: "Note that this can be an expensive operation since all potential users need to be examined."



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)