[ https://issues.apache.org/jira/browse/OAK-2948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14647686#comment-14647686 ]
Nicolas Peltier commented on OAK-2948: -------------------------------------- Hi [~tripod], how complicated would that be to backport this fix in 1.2 branch? I'd need this in an AEM 6.1 project, and using 1.3.2 seems just impossible > Expose DefaultSyncHandler > ------------------------- > > Key: OAK-2948 > URL: https://issues.apache.org/jira/browse/OAK-2948 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: auth-external > Reporter: Konrad Windszus > Fix For: 1.3.2 > > > We do have the use case of extending the user sync. Unfortunately > {{DefaultSyncHandler}} is not exposed, so if you want to change one single > aspect of the user synchronisation you have to copy over the code from the > {{DefaultSyncHandler}}. Would it be possible to make that class part of the > exposed classes, so that deriving your own class from that DefaultSyncHandler > is possible? > Very often company LDAPs are not very standardized. In our case we face an > issue, that the membership is being listed in a user attribute, rather than > in a group attribute. -- This message was sent by Atlassian JIRA (v6.3.4#6332)