Migrate our user management system from OpenLDAP to the 389 Directory Server #57
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
389 is newer, has a Cockpit web interface, and the recommended successor to OpenLDAP. Of course, our OpenLDAP server isn't broken... yet.
This is not too important to do right now since OpenLDAP works perfectly (it's a bit inconvenient sometimes but whatever) so I'm untagging this for v5.0.
Let's try playing around with 389 DS in a VM first to get an idea of what it's like.
All of the LDAP configs are in a repo anyways so the transition shouldn't be too difficult.
OK, so I tried experimenting with 389 DS in a systemd-nspawn container, and it has a nice Cockpit UI but seems very complicated, even more complicated than OpenLDAP. Yeah, I don't think I want to try messing around with it anytime soon.
I don't see much of a point in doing this and don't think we will do this in the near future, so closing for now. OpenLDAP works perfectly fine.