Installation guide

NOTE
To register the Directory Server instance with an existing Configuration Directory Server,
select yes. T his continues with the registration process rather than the regular custom
setup process.
Registering a new instance with a Configuration Directory Server requires you to supply
information about the Configuration Directory Server:
The Configuration Directory Server URL, such as
ldap://ldap.exam ple.com :389/o=NetscapeRoot
To use T LS/SSL, set the protocol as ldaps:// instead of ldap:// For LDAPS, use
the secure port (636) instead of the standard port (389), and provide a CA certificate.
The Configuration Directory Server administrator's user ID; by default, this is adm in.
The administrator user's password.
The Configuration Directory Server Admin domain, such as example.com .
The CA certificate to authenticate to the Configuration Directory Server. This is only
required if the Directory Server instance will connect to the Configuration Directory
Server over LDAPS. This should be the full path and filename the CA certificate in
PEM/ASCII format.
This information is supplied in place of creating an admin user and domain for the new
Directory Server steps 8, 9, and 10.
8. Set the administrator username. T he default is adm in.
9. Set the administrator password and confirm it.
10. Set the administration domain. T his defaults to the host's domain. For example:
Administration Domain [redhat.com]:
11. Enter the Directory Server port number. T he default is 389, but if that port is in use, the setup
program supplies a randomly generated one.
Directory server network port [389]: 1066
12. Enter the Directory Server identifier; this defaults to the hostname.
Directory server identifier [example]:
13. Enter the directory suffix. This defaults to dc=domain name. For example:
Suffix [dc=redhat, dc=com]:
14. Set the Directory Manager username. T he default is cn=Directory Manager.
15. Set the Directory Manager password and confirm it.
16. Select whether you want to install sample entries with the Directory Server instance. T his means
that an example LDIF, with preconfigured users, groups, roles, and other entries, is imported into
the Directory Server database. T his option is helpful for evaluation or testing Directory Server
features.
This is not required.
17. Select whether to populate the Directory Server with data; this means whether to import an LDIF
file with existing data into the Directory Server database. If the answer is yes, then supply a path
to the LDIF file or select the suggested file. If the LDIF file requires custom schema, perform a
Chapter 5. Setting up Red Hat D irectory Server on Sun Solaris
67