[
https://issues.apache.org/jira/browse/OAK-4218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela updated OAK-4218:
------------------------
Attachment: OAK-4218_initialdraft.patch
initial draft based on a discussion with [~frm] that postpones the registration
of the {{SynchronizationMBean}} to the availability of a service references to
{{ContentRepository}} and {{SecurityProvider}}.
> Base SyncMBeanImpl on Oak API
> -----------------------------
>
> Key: OAK-4218
> URL: https://issues.apache.org/jira/browse/OAK-4218
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: auth-external
> Reporter: angela
> Assignee: angela
> Attachments: OAK-4218_initialdraft.patch
>
>
> While looking at the oak-auth-external code base I found that
> {{SyncMBeanImpl}} is based on JCR API while sync called during authentication
> will solely rely on API defined by oak-core.
> This not only limits the implementations to operations that can executed on
> the JCR API but also introduces the risk of inconsistencies.
> As a matter of fact {{ExternalLoginModuleTestBase.createMBean}} also lists
> this as limitation and TODO:
> {quote}
> // todo: how to retrieve JCR repository here? maybe we should base
> the sync mbean on oak directly.
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
