3.5. Custom Setup

3.5. Custom Setup

Custom setup provides two special configuration options that allow you to add information to the Directory Server databases during the setup period. One imports an LDIF file, which is useful if you have existing information. The other imports sample data that is included with Directory Server; this is useful for testing features of Directory Server and for evaluation.


Run the setup-ds-admin.pl script as root.

The custom setup has the following steps:


If Directory Server is already installed on your machine, it is extremely important that you perform a migration, not a fresh installation. Migration is described in Chapter 8, Migrating from Previous Versions.

  1. After the Directory Server packages are installed as described in Section 3.2, “Installing the Directory Server Packages”, then launch the setup-ds-admin.pl script.

    # /usr/sbin/setup-ds-admin.pl
  2. Select y to accept the Red Hat licensing terms.

  3. The dsktune utility runs. Select y to continue with the setup.

    dsktune checks the available disk space, processor type, physical memory, and other system data and settings such as TCP/IP ports and file descriptor settings. If your system does not meet these basic Red Hat Directory Server requirements, dsktune returns a warning. dsktune warnings do not block the setup process; simply entree y to go to the next step.

  4. Next, choose the setup type. Accept the default, option 3, to perform a custom setup.

  5. Set the computer name of the machine on which the Directory Server is being configured. This defaults to the fully-qualified domain name (FQDN) for the host. For example:

    Computer name [ldap.example.com]:


    The setup program gets the host information from the /etc/resolv.conf file. If there are aliases in the /etc/hosts file, such as ldap.example.com, that do not match the /etc/resolv.conf settings, you cannot use the default hostname option.

    The hostname is very important. It is used generate the Directory Server instance name, the admin domain, and the base suffix, among others. If you are using SSL/TLS or Kerberos, the computer name must be the exact name that clients use to connect to the system. If you will use DNS, make sure the name resolves to a valid IP address and that IP address resolves back to this name.

  6. Set the user and group as which the Directory Server process will run. The default is nobody:nobody. For example:

    System User [nobody]:
    System Group [nobody]:
  7. The next step allows you to register your Directory Server with an existing Directory Server instance, called the Configuration Directory Server. This registers the new instance so it can be managed by the Console. If this is the first Directory Server instance set up on your network, it is not possible to register it with another directory. Select n to set up this Directory Server as a Configuration Directory Server and move to the next custom install step, setting up the administrator user.


    To register the Directory Server instance with an existing Configuration Directory Server, select yes. This 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.example.com:389/o=NetscapeRoot

      To use TLS/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 admin.

    • 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. The default is admin.

  9. Set the administrator password and confirm it.

  10. Set the administration domain. This defaults to the host's domain. For example:

    Administration Domain [redhat.com]:
  11. Enter the Directory Server port number. The 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. The 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. This means that an example LDIF, with preconfigured users, groups, roles, and other entries, is imported into the Directory Server database. This 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 silent setup instead, and use the SchemaFile directive in the .inf to specify additional schema files. See Section, “.inf File Directives” for information on .inf directives.

    The default option is none, which does not import any data.

  18. Enter the Administration Server port number. The default is 9830, but if that port is in use, the setup program supplies a randomly generated one.

    Administration port [9830]:
  19. Set an IP address for the new Administration Server to use. The Administration Server uses a web server, and this parameter is set in the console.conf file for the server. Setting this parameter restricts the Administration Server to that single IP. Leaving it blank, the default, allows the Administration Server to acquire any IP address.

  20. Set the user as which the Administration Server process will run. The default is nobody. For example:

    Run Administration Server as [nobody]:
  21. The last screen asks if you are ready to set up your servers. Select yes.

    Are you ready to set up your servers? [yes]:
    Creating directory server . . .
    Your new DS instance 'example3' was successfully created.
    Creating the configuration directory server . . .
    Beginning Admin Server reconfiguration . . .
    Creating Admin Server files and directories . . .
    Updating adm.conf . . .
    Updating admpw . . .
    Registering admin server with the configuration directory server . . .
    Updating adm.conf with information from configuration directory server . . .
    Updating the configuration for the httpd engine . . .
    Restarting admin server . . .
    The admin server was successfully started.
    Admin server was successfully reconfigured and started.
    Exiting . . .
    Log file is '/tmp/setupul88C1.log'

When the setup-ds-admin.pl script is done, then the Directory Server is configured and running. To log into the Directory Server Console to begin setting up your directory service, do the following:

  1. Get the Administration Server port number from the Listen parameter in the console.conf configuration file.

    grep \^Listen /etc/dirsrv/admin-serv/console.conf
  2. Using the Administration Server port number, launch the Console.

    /usr/bin/redhat-idm-console -a http://localhost:9830


If you do not pass the Administration Server port number with the redhat-idm-console command, then you are prompted for it at the Console login screen.

Note: This documentation is provided {and copyrighted} by Red Hat®, Inc. and is released via the Open Publication License. The copyright holder has added the further requirement that Distribution of substantively modified versions of this document is prohibited without the explicit permission of the copyright holder. The CentOS project redistributes these original works (in their unmodified form) as a reference for CentOS-5 because CentOS-5 is built from publicly available, open source SRPMS. The documentation is unmodified to be compliant with upstream distribution policy. Neither CentOS-5 nor the CentOS Project are in any way affiliated with or sponsored by Red Hat®, Inc.