[
https://issues.apache.org/jira/browse/OAK-2948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15014123#comment-15014123
]
Tobias Bocanegra commented on OAK-2948:
---------------------------------------
yeah, the {{DefaultSyncConfigImpl}} separates the configuration for the
{{DefaultSyncHandler}}:
{noformat}
@Component(
label = "Apache Jackrabbit Oak Default Sync Handler",
name =
"org.apache.jackrabbit.oak.spi.security.authentication.external.impl.DefaultSyncHandler",
configurationFactory = true,
metatype = true,
ds = false
)
{noformat}
so basically it's the same as if it would be in the same class as
DefaultSyncHandler. we just separated it so that we can have a own pojo for the
config for non osgi use cases.
If you create your own sync handler, you obviously need your own component
configuration. currently, you need to copy-paste it. correct.
> 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, 1.2.7, 1.0.22
>
>
> 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)
