Sunday, March 6, 2011

389 Directory Server | Fedora Directory Server On CentOS

389 Directory Server

The 389 Directory Server (previously Fedora Directory Server) is an LDAP (Lightweight Directory Access Protocol) server developed by Red Hat, as part of Red Hat's community-supported Fedora Project. 389 Directory Server is identical to the Red Hat Directory Server, just rebranded. The name 389 is derived from the port number for LDAP.


1.) 389 Directory Server has multi-master capability.
2.) 389 Directory Server also has the ability to export parts of the directory to read-only servers. This is similar to the Read Only Domain Controller in Microsoft's Active Directory Domain Services.
3.) 389 Directory Server has a Java-based GUI front end for administration, but the underlying LDAP database can be managed by other LDAP compliant tools.

First you need to download & install epel rpm package, that is repository rpm packages.Then you can install packages with your usual method, and the EPEL repository is included.

[root@server2/etc/dirsrv]#rpm -Uvh

Do a yum install for the 389 directory packages:

[root@server2/etc/dirsrv]#yum install 389-ds openldap-clients

Install Directories….

/var/lib/dirsrv (this is where you directory data lives)

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]:

Do you agree to the license terms? [no]: 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

389 Directory Server system tuning analysis version 10-AUGUST-2007.

NOTICE : System is i686-unknown-linux2.6.18-194.3.1.el5_lustre.1.8.4 (1 processor).

NOTICE : The net.ipv4.tcp_keepalive_time is set to 10200000 milliseconds

(170 minutes). This may cause temporary server congestion from lost client connections.
WARNING: There are only 1024 file descriptors (hard limit) available, which limit the number of simultaneous connections.

WARNING: There are only 1024 file descriptors (soft limit) available, which limit the number of simultaneous connections.

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]: 2

Enter the fully qualified domain name of the computer on which you're setting up server software. Using the form

To accept the default shown in brackets, press the Enter key.

Computer name []:


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]: ldap
System Group [nobody]: ldap

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., 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 (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 []:
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 [server2]:
Error: the server already exists at '/etc/dirsrv/slapd-server2'
Please remove it first if you really want to recreate it,or use a different ServerIdentifier to create another instance.

Directory server identifier [server2]:


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,

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=xais, dc=com]:

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 (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 'server2' 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 . . .
/usr/sbin/semanage: Port tcp/9830 already defined

Starting admin server . . .
The admin server was successfully started.
Admin server was successfully created, configured, and started.
Exiting . . .
Log file is '/tmp/setupotJ3mD.log'


It will show dialog box fill up Username and Password with Server Url(

Now Select Directory Server and click Open. New window will open like below, click at directory tab expand domain tree and click on people.

Creating New User:
Now right click on people and select option new -> user And enter the information for that user.
Now select the Posix User option and enter the required information and click ok.
*Ener Unique UID and GID(Same)
*Home Directory
*Login Shell /bin/bash

Now you have two options, First you can create user’s home directory at client box. And second you can create home directory of the user on server machine. Otherwise you will get “No Directory” message while you are trying to login.I am giving you both the methods.

Home Directory on Server :-
This method is same as windows or AD environment. When you create user’s home directory on server and share with NFS or automatically mount through autofs. Now Login on the server and create user’s home directory.
[root@389ldap ~]# mkdir /home/piyush
[root@389ldap ~]# chown 1001:1001 /home/piyush
[root@389ldap ~]#ll -d /home/piyush
drwxr-xr-x 30 1001 1001 4096 Dec 28 16:03 /home/piyush/
Now share user home directory with NFS
[root@389ldap ~]# vi /etc/exports
/home *(rw,sync)
Now restart nfs service.
[root@389ldap ~]# /etc/init.d/nfs restart
You have done with server setup, Now you need to setup client side.

On Client Side
Home Directory at client machine :-
Login at client box and create user’s directory.
[root@linuxbox ~]# mkdir /home/piyush
[root@linuxbox ~]# chown 1001:1001 /home/piyush
[root@master_hadoop ~]# yum -y install openldap-clients nss_ldap
Once your packages will install, you need to setup authentication section.
[root@master_hadoop ~]# system-config-authentication
#vi /etc/auto.master
/data5/testing123 /etc/auto.home --timeout=60
#vi /etc/auto.home
* -fstype=nfs,rw,soft,intr
Restart autofs service .
[root@master_hadoop ~]# /etc/init.d/autofs restart
Stopping automount: [ OK ]
Starting automount: [ OK ]
[root@master_hadoop ~]#
[root@master_hadoop ~]# vi /etc/nsswitch.conf
passwd: files ldap
shadow: files ldap
group: files ldap
############## Edited
netgroup: nisplus ldap
[root@server2~]#tcpdump port ldap -i eth0 -X -s 1024 -v
[root@server2~]#netstat -tulnap | grep slap