To add an organizational unit (OU) entry to the LDAP tree The examples that follow also presume an InetOrgPerson schema, because the InetOrgPerson schema is delivered with OpenLDAP by default. These instructions will describe how to populate the LDAP tree with organizational units (OUs), groups, and users, all of which are different types of LDAP entries. Now that you have installed and set up Open LDAP, you are ready to add organizational units (see Adding an organizational unit (OU)). For information on how to do this, see the OpenLDAP TLS documentation. (You can delete this file once its content has been added to LDAP, so in this example, we will create it in the /tmp folder.)Īlthough providing instructions is beyond the scope of this tutorial, it is also highly recommended that you set up OpenLDAP to use SSL or TLS security to prevent passwords and other sensitive data from being sent in plain text. An LDAP distinguished name uniquely identifies an LDAP entry. Also note that dc=acme,dc=com is what is called an LDAP distinguished name (DN). Again, you will need to replace 'acme' with your organization's domain name. Because we are assuming that the organization is called Acme Corporation, and that the domain is ',' we will create a domain controller LDAP entry called dc=acme,dc=com. Root entries are usually a special type of entry called a domain controller (DC). In order to build our LDAP tree we must first create the root entry. In this tutorial we will build entries based on the InetOrgPerson schema (which ships with OpenLDAP by default). The attributes in each entry are determined by the LDAP schema. Nodes in this tree are called LDAP 'entries' and may represent users, groups, organizational units, domain controllers, or other objects. Now, you must manually create the 'dc=acme,dc=com' LDAP entry in your LDAP tree.Īn LDAP directory is analogous to a tree.

Ldapsearch centos package