Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
Description
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:
// todo: how to retrieve JCR repository here? maybe we should base the sync mbean on oak directly.