Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
Description
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.
Attachments
Issue Links
- relates to
-
OAK-3522 DefaultSyncContext exposes internal path-utility method
- Closed