jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Konrad Windszus (JIRA)" <j...@apache.org>
Subject [jira] [Created] (OAK-2948) Expose DefaultSyncHandler
Date Tue, 02 Jun 2015 10:04:17 GMT
Konrad Windszus created OAK-2948:
------------------------------------

             Summary: 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


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)

Mime
View raw message