Hot answers tagged openldap
No, if you understand it, it becomes pretty simple and more effective as you don't have to restart the OpenLDAP server after a config change. As you may have noticed, /etc/ldap/slapd.d is a directory, not a file and it contains a set of LDIF files that together create a complete LDAP tree named cn=config. You modify this tree not by editing files, but by ...
It seems you're testing the LDAP bind with a different dn than what postgres constructs: cn=test user,ou=users,dc=example,dc=hyd,dc=com vs "cn=" + "test" + ", ou=users, dc=example, dc=hyd, dc=com" i.e. "test" doesn't match "test user"
There is no best way. You have to think long and hard about how you want to use your data in order to structure it in a way that makes most sense for you, and also look into how your client software will use the directory. As an example, if the structure of your company relies on strict separation, a tree like in your eDirectory example might be useful. ...
cn=admin,dc=domain,dc=com is the administrator for your main database, but probably not for the OLC. By default, connecting as the root user over ldapi:// allows you to manage the configuration. As root: ldapsearch -Y EXTERNAL -H ldapi:// -b cn=config
Only top voted, non community-wiki answers of a minimum length are eligible