3 ms·

> I had nothing but pain with openLDAP. Every guide I could find trying to learn gave examples using the 'old config format' even though the newer db config fo

> I had nothing but pain with openLDAP. Every guide I could find trying to learn gave examples using the 'old config format' even though the newer db config format had been around for many, many years at that time. This is a poor excuse. While the flat file (slapd.conf) is deprecated in 2.4, it still works fine if you don't mind restarting to apply changes, and you can easily switch from slapd.conf to back-config (but not the other way) when you are finished getting a new stack up.

ansible 8y ago
> This is a poor excuse. I encourage you to look at things from the perspective of someone new to LDAP, or maybe someone new to directory services in general. LDAP already introduces its own terminology which is a little confusing at first. And it is an object database, which will be less familiar to many people than a relational database. Add to that the 'database number' thing when it might not be clear to beginners what is going into which one and why.
- philjohn 8y ago
  If you're totally new to LDAP (which despite being "just an object database" has many bells and whistles to fit into various deployments) there is always going to be a little friction at first - there's a reason people make good money offering consultancy and support for LDAP servers. It's not something you're going to be able to get setup and running in an afternoon, and that's fine, some things are too complex to just be thrown together.
amaccuish 8y ago
Sorry but I can only agree with parent. Not only was there no up to date documentation, I couldn't even find out how to revert back to offline config. I gave up and looked elsewhere, and I consider myself fairly experienced with LDAP and other products. Even when I worked out how to do online config, if I made a mistake and the service wouldn't start, I couldn't work out how to manually revert the change so the service could start again.

ansible 8y ago

> This is a poor excuse. I encourage you to look at things from the perspective of someone new to LDAP, or maybe someone new to directory services in general. LDAP already introduces its own terminology which is a little confusing at first. And it is an object database, which will be less familiar to many people than a relational database. Add to that the 'database number' thing when it might not be clear to beginners what is going into which one and why.

philjohn 8y ago
If you're totally new to LDAP (which despite being "just an object database" has many bells and whistles to fit into various deployments) there is always going to be a little friction at first - there's a reason people make good money offering consultancy and support for LDAP servers. It's not something you're going to be able to get setup and running in an afternoon, and that's fine, some things are too complex to just be thrown together.

amaccuish 8y ago

Sorry but I can only agree with parent. Not only was there no up to date documentation, I couldn't even find out how to revert back to offline config. I gave up and looked elsewhere, and I consider myself fairly experienced with LDAP and other products. Even when I worked out how to do online config, if I made a mistake and the service wouldn't start, I couldn't work out how to manually revert the change so the service could start again.