jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tobias Bocanegra (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-2948) Expose DefaultSyncHandler
Date Tue, 02 Jun 2015 16:42:50 GMT

    [ https://issues.apache.org/jira/browse/OAK-2948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14569390#comment-14569390

Tobias Bocanegra commented on OAK-2948:

this request came up recently elsewhere. I think it makes sense - although extending an osgi
service is usually not such a good idea. but we could split the handler in a service and a
handler part, and expose the later.

> 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

View raw message