Working With Oracle® Solaris 11.2 Directory and Naming Services: LDAP

Exit Print View

Updated: July 2014
 
 

Populating the LDAP Server with Data

After the DIT is created, you populate the information tree with data. The data is derived from all systems that contain /etc files. Therefore, you must perform this task on those systems rather than on the server. The manner of populating the information tree depends on the planning that was described in Planning the LDAP Data Population.

Examples of files whose data would fill the information tree are:

  • aliases

  • auto_*

  • bootparams

  • ethers

  • group

  • hosts

Similarly, information from rights-related files in /etc are also added to the information tree, such as user_attr, ~/security/auth_attr, ~/security/prof_attr, and ~/security/exec_attr.

To populate the information tree, you use the ldapaddent command. You also specify the /etc file or database whose data you are loading on the tree. Some files must be loaded in sequence to obtain better performance. The files and their loading sequence are as follows:

  1. passwd

  2. shadow

  3. networks

  4. netmasks

  5. bootparams

  6. ethers

Note that when you are loading automounter information, the file or database name uses the naming format auto_*, such as auto_home.


Note -  Before populating the directory server with data, you must configure the server to store passwords in UNIX Crypt format if you are using the pam_unix_* modules. If you are using pam_ldap, you can store passwords in any format. For more information about setting the password in UNIX crypt format, see the Oracle Directory Server Enterprise Edition documents. For details about the ldapaddent command, see the ldapaddent (1M) man page.