[
https://issues.apache.org/jira/browse/OAK-4154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15288524#comment-15288524
]
angela commented on OAK-4154:
-----------------------------
[~baedke], i find the description still misleading:
{quote}
[...] additional boolean argument to enable or disable group sync during the
call
{quote}
this is _not_ what the {{forceGroupSync}} flag does. you can't disable group
sync with this flag! the only thing you achieve is preventing a forced group
sync for groups that have not yet expired which is something quite different
IMHO.
and as i said above: if it's really about offering the ability to manipulate
the {{forceGroupSync}}, I would suggest to also expose {{{{forceUserSync}} as
this would also allow to reduce the amount of users to be synchronized (namely
those that haven't expired)... in particular in the *All*-methods.
> SynchronizationMBean should offer methods to synchronize without forcing
> group sync.
> ------------------------------------------------------------------------------------
>
> Key: OAK-4154
> URL: https://issues.apache.org/jira/browse/OAK-4154
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: auth-external
> Reporter: Manfred Baedke
> Assignee: Manfred Baedke
> Fix For: 1.6
>
>
> SynchronizationMBean.syncUsers(...) and related methods always force the
> synchronization of groups (indirectly) containing the user, independently of
> any configured expiration intervals. This may have a huge negative impact on
> the performance of these methods.
> Additional methods should be added to the interface
> org.apache.jackrabbit.oak.spi.security.authentication.external.impl.jmx.SynchronizationMBean,
> featuring an additional boolean argument to enable or disable group sync
> during the call
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
