In the realm of enterprise-class open source LDAP servers for Linux, the 389 Directory Server stands out. This server, which is based on the Fedora Directory Server, is a robust and reliable solution for managing your network resources.
This guide will take you through the process of setting up and configuring the 389 Directory Server on a CentOS 6.2 server. Before we delve into the details, ensure that your server’s hostname and Fully Qualified Domain Name (FQDN) are correctly configured.
Running the Configuration Script
The first step in setting up the 389 Directory Server is to run the configuration script. This can be done by executing the following command:
setup-ds-admin.pl
This command initiates the setup process for the 389 Directory and Administration Servers. It is recommended to run this script with “root” privileges for a smooth setup process. The script provides prompts and tips to guide you through the setup process.
Examples complete setup and 389 directory configuration :
[root@centos62 ~]# setup-ds-admin.pl
==============================================================================
This program will set up the 389 Directory and Administration Servers.
It is recommended that you have "root" privilege to set up the software.
Tips for using this program:
- Press "Enter" to choose the default and go to the next screen
- Type "Control-B" then "Enter" to go back to the previous screen
- Type "Control-C" to cancel the setup program
Would you like to continue with set up? [yes]: yes
==============================================================================
Your system has been scanned for potential problems, missing patches,
etc. The following output is a report of the items found that need to
be addressed before running this software in a production
environment.
389 Directory Server system tuning analysis version 10-AUGUST-2007.
NOTICE : System is i686-unknown-linux2.6.32-220.4.1.el6.i686 (1 processor).
Would you like to continue? [no]: yes
==============================================================================
Choose a setup type:
1. Express
Allows you to quickly set up the servers using the most
common options and pre-defined defaults. Useful for quick
evaluation of the products.
2. Typical
Allows you to specify common defaults and options.
3. Custom
Allows you to specify more advanced options. This is
recommended for experienced server administrators only.
To accept the default shown in brackets, press the Enter key.
Choose a setup type [2]:
==============================================================================
Enter the fully qualified domain name of the computer
on which you're setting up server software. Using the form
.
Example: eros.example.com.
To accept the default shown in brackets, press the Enter key.
Warning: This step may take a few minutes if your DNS servers
can not be reached or if DNS is not configured correctly. If
you would rather not wait, hit Ctrl-C and run this program again
with the following command line option to specify the hostname:
General.FullMachineName=your.hostname.domain.name
Computer name [centos62.webhostinggeeks.local]:
==============================================================================
The servers must run as a specific user in a specific group.
It is strongly recommended that this user should have no privileges
on the computer (i.e. a non-root user). The setup procedure
will give this user/group some permissions in specific paths/files
to perform server-specific operations.
If you have not yet created a user and group for the servers,
create this user and group using your native operating
system utilities.
System User [nobody]:
System Group [nobody]:
==============================================================================
Server information is stored in the configuration directory server.
This information is used by the console and administration server to
configure and manage your servers. If you have already set up a
configuration directory server, you should register any servers you
set up or create with the configuration server. To do so, the
following information about the configuration server is required: the
fully qualified host name of the form
.(e.g. hostname.example.com), the port number
(default 389), the suffix, the DN and password of a user having
permission to write the configuration information, usually the
configuration directory administrator, and if you are using security
(TLS/SSL). If you are using TLS/SSL, specify the TLS/SSL (LDAPS) port
number (default 636) instead of the regular LDAP port number, and
provide the CA certificate (in PEM/ASCII format).
If you do not yet have a configuration directory server, enter 'No' to
be prompted to set up one.
Do you want to register this software with an existing
configuration directory server? [no]:
==============================================================================
Please enter the administrator ID for the configuration directory
server. This is the ID typically used to log in to the console. You
will also be prompted for the password.
Configuration directory server
administrator ID [admin]:
Password:
Password (confirm):
==============================================================================
The information stored in the configuration directory server can be
separated into different Administration Domains. If you are managing
multiple software releases at the same time, or managing information
about multiple domains, you may use the Administration Domain to keep
them separate.
If you are not using administrative domains, press Enter to select the
default. Otherwise, enter some descriptive, unique name for the
administration domain, such as the name of the organization
responsible for managing the domain.
Administration Domain [webhostinggeeks.local]:
==============================================================================
The standard directory server network port number is 389. However, if
you are not logged as the superuser, or port 389 is in use, the
default value will be a random unused port number greater than 1024.
If you want to use port 389, make sure that you are logged in as the
superuser, that port 389 is not in use.
Directory server network port [389]:
==============================================================================
Each instance of a directory server requires a unique identifier.
This identifier is used to name the various
instance specific files and directories in the file system,
as well as for other uses as a server instance identifier.
Directory server identifier [centos62]:
==============================================================================
The suffix is the root of your directory tree. The suffix must be a valid DN.
It is recommended that you use the dc=domaincomponent suffix convention.
For example, if your domain is example.com,
you should use dc=example,dc=com for your suffix.
Setup will create this initial suffix for you,
but you may have more than one suffix.
Use the directory server utilities to create additional suffixes.
Suffix [dc=webhostinggeeks, dc=local]:
==============================================================================
Certain directory server operations require an administrative user.
This user is referred to as the Directory Manager and typically has a
bind Distinguished Name (DN) of cn=Directory Manager.
You will also be prompted for the password for this user. The password must
be at least 8 characters long, and contain no spaces.
Press Control-B or type the word "back", then Enter to back up and start over.
Directory Manager DN [cn=Directory Manager]:
Password:
Password (confirm):
==============================================================================
The Administration Server is separate from any of your web or application
servers since it listens to a different port and access to it is
restricted.
Pick a port number between 1024 and 65535 to run your Administration
Server on. You should NOT use a port number which you plan to
run a web or application server on, rather, select a number which you
will remember and which will not be used for anything else.
Administration port [9830]:
==============================================================================
The interactive phase is complete. The script will now set up your
servers. Enter No or go Back if you want to change something.
Are you ready to set up your servers? [yes]:
Creating directory server . . .
Your new DS instance 'centos62' was successfully created.
Creating the configuration directory server . . .
Beginning Admin Server creation . . .
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 . . .
Starting admin server . . .
output: Starting dirsrv-admin:
output: [ OK ]
The admin server was successfully started.
Admin server was successfully created, configured, and started.
Exiting . . .
Log file is '/tmp/setup1EmS4N.log'
System Scanning and Setup Type Selection
Upon running the configuration script, your system will be scanned for potential issues, missing patches, and other elements that need to be addressed before the software can run in a production environment. After the system scan, you will be prompted to choose a setup type. The options are:
- Express: This option allows you to quickly set up the servers using the most common options and pre-defined defaults. It is useful for a quick evaluation of the products.
- Typical: This option allows you to specify common defaults and options.
- Custom: This option allows you to specify more advanced options. It is recommended for experienced server administrators only.
Server Information and User Configuration
The configuration script will ask for the fully qualified domain name of the computer on which you’re setting up server software. It will also prompt you to specify a system user and group under which the servers must run. It is strongly recommended that this user should have no privileges on the computer (i.e., a non-root user). The setup procedure will give this user/group some permissions in specific paths/files to perform server-specific operations.
Configuration Directory Server
Server information is stored in the configuration directory server. This information is used by the console and administration server to configure and manage your servers. If you have already set up a configuration directory server, you should register any servers you set up or create with the configuration server. If you do not yet have a configuration directory server, you will be prompted to set one up.
Administration Domain and Network Port
The information stored in the configuration directory server can be separated into different Administration Domains. If you are managing multiple software releases at the same time, or managing information about multiple domains, you may use the Administration Domain to keep them separate.
The standard directory server network port number is 389. However, if you are not logged in as the superuser, or port 389 is in use, the default value will be a random unused port number greater than 1024.
Directory Server Identifier and Suffix
Each instance of a directory server requires a unique identifier. This identifier is used to name the various instance-specific files and directories in the file system, as well as for other uses as a server instance identifier.
The suffix is the root ofyour directory tree. The suffix must be a valid DN. It is recommended that you use the dc=domaincomponent suffix convention. For example, if your domain is example.com, you should use dc=example,dc=com for your suffix. Setup will create this initial suffix for you, but you may have more than one suffix. Use the directory server utilities to create additional suffixes.
Directory Manager and Administration Server
Certain directory server operations require an administrative user. This user is referred to as the Directory Manager and typically has a bind Distinguished Name (DN) of cn=Directory Manager. You will also be prompted for the password for this user. The password must be at least 8 characters long, and contain no spaces.
The Administration Server is separate from any of your web or application servers since it listens to a different port and access to it is restricted. Pick a port number between 1024 and 65535 to run your Administration Server on. You should NOT use a port number which you plan to run a web or application server on, rather, select a number which you will remember and which will not be used for anything else.
Finalizing the Setup
Once you’ve completed the interactive phase, the script will set up your servers. If you want to change something, you can enter ‘No’ or go ‘Back’. If you’re ready to proceed, the script will create the directory server, the configuration directory server, and the admin server. It will also start the admin server and provide you with a log file for reference.
Commands Mentioned
- setup-ds-admin.pl – This command initiates the setup process for the 389 Directory and Administration Servers.
Conclusion
Setting up and configuring the 389 Directory Server on CentOS 6.2 involves a series of steps that require careful attention. From running the configuration script to finalizing the setup, each step is crucial for the successful operation of the server. Remember, the 389 Directory Server is a powerful tool for managing your network resources. With this guide, you should be able to set up and configure your 389 Directory Server with ease.
For more insights into different server types like Apache, Nginx, and LiteSpeed, or hosting options like dedicated server, VPS server, cloud hosting, and shared hosting, visit our website.
FAQ
-
What is the 389 Directory Server?
The 389 Directory Server is an enterprise-class open source LDAP server for Linux. It is based on the Fedora Directory Server and is used for managing network resources.
-
What is the purpose of the configuration script in the 389 Directory Server setup?
The configuration script initiates the setup process for the 389 Directory and Administration Servers. It provides prompts and tips to guide you through the setup process.
-
What is the role of the Directory Manager in the 389 Directory Server?
The Directory Manager is an administrative user required for certain directory server operations. This user typically has a bind Distinguished Name (DN) of cn=Directory Manager.
-
What is the Administration Server in the context of the 389 Directory Server?
The Administration Server is separate from any of your web or application servers as it listens to a different port and access to it is restricted. It is used to manage and configure your servers.
-
What is the significance of the suffix in the 389 Directory Server setup?
The suffix is the root of your directory tree. It must be a valid DN and is recommended to use the dc=domaincomponent suffix convention. The setup creates this initial suffix, but you may have more than one suffix.
