[
https://issues.apache.org/jira/browse/OAK-4154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15424460#comment-15424460
]
angela commented on OAK-4154:
-----------------------------
since for whatever reason this issue showed up in a backport issue:
i am -1 for the original proposal and the commit without a single test case.
before committing any new code for this issue, we have to reach consensus
- if that is sensible and needed in the light of the dynamic membership
- agree on the best way to do this (my take would be to have 1 flag that
respects expiration of both users and groups and not just do it for groups)
- provide proper test coverage
- provide benchmarks that illustrates the performance gains associated with
this compared and in combination with dynamic membership
> 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
>
> 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)
