[GH-ISSUE #717] [RFE] Synchronisation With External IDM #259

Open
opened 2026-02-27 08:16:13 +03:00 by kerem · 0 comments
Owner

Originally created by @Firstyear on GitHub (Oct 27, 2023).
Original GitHub issue: https://github.com/lldap/lldap/issues/717

It was recently requested that some users may have an interest in running LLDAP as their primary data source, while then synchronising the user data to other IDM's for their features. The listed example for this was Kanidm.

To achieve this, from the LLDAP side the following changes would be required.

  • Implementation of rfc4533 content sync
    • This would rely upon a "last modified time stamp" on each entry so that changed entries can be identified.
  • Exposing details about the OPAQUE storage mechanism (optional, and may not be needed)

See Also: https://github.com/kanidm/kanidm/issues/2259

Originally created by @Firstyear on GitHub (Oct 27, 2023). Original GitHub issue: https://github.com/lldap/lldap/issues/717 It was recently requested that some users may have an interest in running LLDAP as their primary data source, while then synchronising the user data to other IDM's for their features. The listed example for this was Kanidm. To achieve this, from the LLDAP side the following changes would be required. * Implementation of [rfc4533 content sync](https://www.rfc-editor.org/rfc/rfc4533) * This would rely upon a "last modified time stamp" on each entry so that changed entries can be identified. * Exposing details about the OPAQUE storage mechanism (optional, and may not be needed) See Also: https://github.com/kanidm/kanidm/issues/2259
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/lldap-lldap#259
No description provided.