How to Install and Setup 389 Directory Server on CentOS 7

Setup 389 Directory Server389 Directory Server (previously Fedora Directory Server) is an open source enterprise class LDAP server for Linux. It is developed by Red Hat community-supported Fedora Project. The name 389 is derived from the port number for LDAP.

In this article we will guide you through the steps on how to install and setup 389 directory server on CentOS 7.

Steps to Install and Setup 389 Directory Server on CentOS 7

1. Turn off selinux :

vi /etc/sysconfig/selinux

Change SELINUX to disabled then reboot the server :

# This file controls the state of SELinux on the system.
# SELINUX= can take one of these three values:
#     enforcing - SELinux security policy is enforced.
#     permissive - SELinux prints warnings instead of enforcing.
#     disabled - No SELinux policy is loaded.
SELINUX=disabled
# SELINUXTYPE= can take one of three two values:
#     targeted - Targeted processes are protected,
#     minimum - Modification of targeted policy. Only selected processes are protected.
#     mls - Multi Level Security protection.
SELINUXTYPE=targeted

2. Perform basic performance and Security tuning for LDAP server :

# vi /etc/sysctl.conf

Add the following :

net.ipv4.tcp_keepalive_time = 300
net.ipv4.ip_local_port_range = 1024 65000
fs.file-max = 64000
# vi /etc/security/limits.conf

Add the following :

* soft nofile 524288
* hard nofile 524288

3. Reboot the server. This is to take effect the SELINUX and performance tuning setting :

# reboot

4. Install 389 directory packages :

# yum install https://dl.fedoraproject.org/pub/epel/7/x86_64/e/epel-release-7-6.noarch.rpm
# yum install 389-* -y

5. Create ldap user and set its password :

# useradd ldap
# passwd ldap

6. Start 389 installation :

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

==============================================================================
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 23-FEBRUARY-2012.

NOTICE : System is x86_64-unknown-linux3.10.0-327.4.5.el7.x86_64 (2 processors).

Would you like to continue? [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 [centos72.ehowstuff.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]: 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. 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 [ehowstuff.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 [centos72]:

==============================================================================
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=ehowstuff, 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 'centos72' was successfully created.
Creating the configuration directory server . . .
Beginning Admin Server creation . . .
Creating Admin Server files and directories . . .

7. Start the dirsrv admin service and dirsrv instance :

# systemctl start dirsrv-admin
# systemctl start dirsrv@centos72

8. Configure dirsrv admin service and all dirsrv instance auto start at boot :

# systemctl enable dirsrv.target && systemctl enable dirsrv-admin

9. Allow management and directory service ports :

# firewall-cmd --permanent --add-port=389/tcp
# firewall-cmd --permanent --add-port=636/tcp
# firewall-cmd --permanent --add-port=9830/tcp
# firewall-cmd --reload

10. Verify all the allowed ports :

# firewall-cmd --list-all
public (default, active)
  interfaces: ens160
  sources:
  services: dhcpv6-client ssh
  ports: 389/tcp 9830/tcp 80/tcp 636/tcp
  masquerade: no
  forward-ports:
  icmp-blocks:
  rich rules:

11. Login to your 389 directory from console.

Setup 389 Directory Server

12. Your 389 directory administration console will look as below :

Setup 389 Directory Server

How to Install and Configure 389 LDAP Directory Server on CentOS 6.5

Install and Configure 389 LDAPA directory server provides a centralized directory service for your organization. It is alternative to windows active directory. This post will describes how to install and configure 389 LDAP Directory Server with a basic Lightweight Directory Access Protocol (LDAP) directory implementation. 389 Directory Server was formerly known as the Fedora Directory Server and it is an enterprise-class open source LDAP. 389 Directory server has been developed by Red Hat, as part of Red Hat’s community-supported Fedora Project.

Steps to Install and Configure 389 LDAP Directory Server

TCP and Files system Tuning :
a) Decrease the time default value for tcp_keepalive_time connection. Edit the /etc/sysctl.conf file and add the following lines to the bottom of sysctl.conf ”

[root@ldap ~]# echo "net.ipv4.tcp_keepalive_time = 300" >> /etc/sysctl.conf
b) Increase number of local system ports available by editing this parameter in the /etc/sysctl.conf file :
[root@ldap ~]# echo "net.ipv4.ip_local_port_range = 1024 65000" >> /etc/sysctl.conf

c) Increase the file descriptors by running these commands:

[root@ldap ~]# echo "64000" > /proc/sys/fs/file-max
[root@ldap-05 ~]# echo "fs.file-max = 64000" >> /etc/sysctl.conf

d) Increase ulimit in /etc/profile :

[root@ldap ~]# echo "ulimit -n 8192" >> /etc/profile

389 Installation :

1. Prepare EPEL Repository on CentOS 6 :
How to Prepare EPEL Repository on CentOS 6

What packages and versions are available in EPEL?
You can take a look on any of the available EPEL mirrors from our mirror list

Alternately, you can browse the package set using repoview:

2. Configure hostname, FQDN and host file has been configured correctly :

127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
::1         localhost localhost.localdomain localhost6 localhost6.localdomain6

192.168.0.5     ldap.ehowstuff.local

3. Make sure selinux is disabled :
Disable SELinux on CentOS 6.5

4. Install the 389 Directory Server packages :

[root@ldap ~]# yum install 389-ds -y

5. Fix Error: command ‘getsebool httpd_can_connect_ldap’ failed – output [getsebool: SELinux is disabled :

[root@ldap ~]# mkdir ~/bin
[root@ldap ~]# vi ~/bin/getsebool
#!/bin/sh
echo on
exit 0
[root@ldap ~]# vi ~/bin/setsebool
#!/bin/sh
exit 0
[root@ldap ~]# chmod +x ~/bin/*sebool

6. Run setup script to start configure the ldap service :

[root@ldap ~]# PATH=~/bin:$PATH 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]:

==============================================================================
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 23-FEBRUARY-2012.

NOTICE : System is x86_64-unknown-linux2.6.32-431.el6.x86_64 (1 processor).

Would you like to continue? [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 [ldap.ehowstuff.local]:

WARNING: There are problems with the hostname.
Hostname 'ldap.ehowstuff.local' is valid, but none of the IP addresses
resolve back to ldap.ehowstuff.local
- address 192.168.0.5 resolves to host centos6.5.ehowstuff.local

Please check the spelling of the hostname and/or your network configuration.
If you proceed with this hostname, you may encounter problems.

Do you want to proceed with hostname 'ldap.ehowstuff.local'? [no]: yes

==============================================================================
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 [ehowstuff.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 [ldap]:

==============================================================================
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=ehowstuff, 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 . . .
Warning: Hostname ldap.ehowstuff.local is valid, but none of the IP addresses
resolve back to ldap.ehowstuff.local
        address 192.168.0.5 resolves to host centos6.5.ehowstuff.local
Your new DS instance 'ldap' 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 . . .
Starting admin server . . .
output: Starting dirsrv-admin:
output:                                                    [  OK  ]
The admin server was successfully started.
Admin server was successfully reconfigured and started.
Exiting . . .
Log file is '/tmp/setupGwS8hs.log'

7. Start dirsrv and dirsrv-admin service :

[root@ldap ~]# /etc/init.d/dirsrv start
[root@ldap ~]# /etc/init.d/dirsrv-admin start

8. Make dirsrv and dirsrv-admin service auto start at boot :

[root@ldap ~]# chkconfig dirsrv on
[root@ldap ~]# chkconfig dirsrv-admin on

9. Configure Iptables to allow server listen on port 22, 389 and 9830 :

# Firewall configuration written by system-config-firewall
# Manual customization of this file is not recommended.
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
-A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
-A INPUT -p icmp -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 389 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 9830 -j ACCEPT
-A INPUT -j REJECT --reject-with icmp-host-prohibited
-A FORWARD -j REJECT --reject-with icmp-host-prohibited
COMMIT

Restart iptables to take effect the changes :

[root@ldap ~]# service iptables restart
iptables: Applying firewall rules: [ OK ]

10. Verify port listen by the server using netstat :

[root@ldap ~]# netstat -plunt | grep LISTEN
tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 1083/rpcbind
tcp 0 0 0.0.0.0:10000 0.0.0.0:* LISTEN 1125/perl
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 1116/sshd
tcp 0 0 0.0.0.0:9830 0.0.0.0:* LISTEN 1508/httpd.worker
tcp 0 0 127.0.0.1:9000 0.0.0.0:* LISTEN 1126/php-fpm
tcp 0 0 :::8140 :::* LISTEN 1161/httpd
tcp 0 0 :::111 :::* LISTEN 1083/rpcbind
tcp 0 0 :::80 :::* LISTEN 1161/httpd
tcp 0 0 :::22 :::* LISTEN 1116/sshd
tcp 0 0 :::443 :::* LISTEN 1161/httpd
tcp 0 0 :::8443 :::* LISTEN 1161/httpd
tcp 0 0 :::389 :::* LISTEN 1391/./ns-slapd

11. Verify port listen by the server and opened by iptables firewall :

[root@ldap ~]# iptables -nL
Chain INPUT (policy ACCEPT)
target prot opt source destination
ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 state RELATED,ESTABLISHED
ACCEPT icmp -- 0.0.0.0/0 0.0.0.0/0
ACCEPT all -- 0.0.0.0/0 0.0.0.0/0
ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:22
ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:389
ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:9830
REJECT all -- 0.0.0.0/0 0.0.0.0/0 reject-with icmp-host-prohibited

Chain FORWARD (policy ACCEPT)
target prot opt source destination
REJECT all -- 0.0.0.0/0 0.0.0.0/0 reject-with icmp-host-prohibited

Chain OUTPUT (policy ACCEPT)
target prot opt source destination

Ldapsearch Examples for 389 Directory

This post will show you the list of ldapsearch examples for 389 Directory. This ldapsearch examples assumes the following:

a)This ldapsearch is search for uid in the directory.
b)The 389 directory is configured to not support anonymous access, then the user “Directory Manager” and the password is required
c)This ldapsearch command has been run on the 389 server itself, so “localhost” for host is enough.
d)The server uses port number 389. Since this is the default port, the port number does not have to be sent in the search request.

-D binddn  bind DN
-b basedn  base dn for search
-h host    LDAP server
-w passwd  bind password (for simple authentication)
-W         prompt for bind password (Recommended to use this to hide password)
ldapsearch -h localhost -D "cn=Directory Manager" -W -b dc=ehowstuff,dc=local uid=user1

Example :

[root@ldapmaster-11 ~]# ldapsearch -h localhost -D "cn=Directory Manager" -W -b dc=ehowstuff,dc=local uid=user1
Enter LDAP Password:
# extended LDIF
#
# LDAPv3
# base  with scope subtree
# filter: uid=user1
# requesting: ALL
#

# user1, ehowstuff.local
dn: uid=user1,dc=ehowstuff,dc=local
uid: user1
givenName: user1
objectClass: top
objectClass: person
objectClass: organizationalPerson
objectClass: inetorgperson
sn: test
cn: user1 test
userPassword:: e1NTSEF9eTdNQTcyNUxnNjNPRXUxNUVkYk84TEJlTmp3M2d3Z3VoVEIreHc9PQ=
 =

# search result
search: 2
result: 0 Success

# numResponses: 2
# numEntries: 1

How to Change 389 LDAP Password using PHP Scripting

Change 389 LDAP PasswordThis article has been prepared for the purpose of future reference for system administrator. It will describe how to change 389 ldap password using PHP scripting. In order to use this PHP script, you just need to change few parameters and also tested on CentOS 6.5. 389 LDAP Directory is an enterprise-class Open Source LDAP server for GNU/Linux. It is hardened by real-world use, is full-featured, supports multi-master replication, and already handles many of the largest LDAP deployments in the world.

Steps to Change 389 LDAP Password using PHP Scripting

1. Make sure your 389 ldap has been configure correctly :
2. Install php-ldap package into your apache server :

[root@ldapmaster-11 ~]# yum install php-ldap -y

3. Create changepassword.php file and put it into your apache root directory :

[root@ldapmaster-11 ~]# vim /var/www/html/changepassword.php

Modify the $server and $dn in .php file :

<?php
$message = array();

function changePassword($user,$oldPassword,$newPassword,$newPasswordCnf){
  global $message;

  $server = "localhost";
  $dn = "dc=ehowstuff,dc=local";
  $userid = $user;

  $user = "uid=".$user.",".$dn;
  error_reporting(0);
  ldap_connect($server);
  $con = ldap_connect($server);
  ldap_set_option($con, LDAP_OPT_PROTOCOL_VERSION, 3);

  // bind anon and find user by uid
  $sr = ldap_search($con,$dn,"(uid=*)");
  $records = ldap_get_entries($con, $sr);

  $message[] = "Username: " . $userid;
  //$message[] = "DN: " . $user;
  //$message[] = "Current Pass: " . $oldPassword;
  //$message[] = "New Pass: " . $newPassword;

  /* try to bind as that user */
  if (ldap_bind($con, $user, $oldPassword) === false) {
    $message[] = "Error E101 - Current Username or Password is wrong.";
    return false;
  }
  if ($newPassword != $newPasswordCnf ) {
    $message[] = "Error E102 - Your New passwords do not match! ";
    return false;
  }
  if (strlen($newPassword) < 4 ) {
    $message[] = "Error E103 - Your new password is too short! ";
    return false;
  }
  if (!preg_match("/[0-9]/",$newPassword)) {
    $message[] = "Error E104 - Your new password must contain at least one digit. ";
    return false;
  }
  if (!preg_match("/[a-zA-Z]/",$newPassword)) {
    $message[] = "Error E105 - Your new password must contain at least one letter. ";
    return false;
  }
  if (!preg_match("/[A-Z]/",$newPassword)) {
    $message[] = "Error E106 - Your new password must contain at least one uppercase letter. ";
    return false;
  }
  if (!preg_match("/[a-z]/",$newPassword)) {
    $message[] = "Error E107 - Your new password must contain at least one lowercase letter. ";
    return false;
  }

  /* change the password finally */
  $entry = array();
  $entry["userPassword"] = "{SHA}" . base64_encode( pack( "H*", sha1( $newPassword ) ) );

  if (ldap_modify($con,$user,$entry) === false){
    $message[] = "E200 - Your password cannot be change, please contact the administrator.";
  } else {
    $message[] = " Your password has been changed. ";
    //mail($records[0]["mail"][0],"Password change notice : ".$userid," Your password has just been changed.");
  }
}

?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
  <title>Change your LDAP password</title>
  <style type="text/css">
  body { font-family: Verdana,Arial,Courier New; font-size: 0.7em;  }
  input:focus { background-color: #eee; border-color: red; }
  th { text-align: right; padding: 0.8em; }
  #container { text-align: center; width: 500px; margin: 5% auto; }
  ul { text-align: left; list-style-type: square; }
  .msg { margin: 0 auto; text-align: center; color: navy;  border-top: 1px solid red;  border-bottom: 1px solid red;  }
  </style>
  <meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
</head>
<body>
  <div id="container">
    <h2>Change your LDAP password</h2>
<ul>
  <li> Your new password must be 8 characters long and contain at least one letter and one digit. </li>
</ul>
    <form action="<?php print $_SERVER['PHP_SELF']; ?>" name="passwordChange" method="post">
      <table style="width: 400px; margin: 0 auto;">
        <tr><th>Username:</th><td><input name="username" type="text" size="20" autocomplete="off" /></td></tr>
        <tr><th>Old password:</th><td><input name="oldPassword" size="20" type="password" /></td></tr>
        <tr><th>New password:</th><td><input name="newPassword1" size="20" type="password" /></td></tr>
        <tr><th>New password (again):</th><td><input name="newPassword2" size="20" type="password" /></td></tr>
        <tr><td colspan="2" style="text-align: center;" >
          <input name="submitted" type="submit" value="Change Password"/>
          <button onclick="$('frm').action='changepassword.php';$('frm').submit();">Cancel</button>
        </td></tr>
      </table>
    </form>
    <div class="msg"><?php
      if (isset($_POST["submitted"])) {
        changePassword($_POST['username'],$_POST['oldPassword'],$_POST['newPassword1'],$_POST['newPassword2']);
        foreach ( $message as $one ) { echo "<p>$one</p>"; }
      } ?>
    </div>
  </div>
</body>
</html>

Reference :
https://gist.github.com/657334/98d7c111796db51059a5fd788240fd69672b8daf
http://ideone.com/Ib90W
http://technology.mattrude.com/2010/11/ldap-php-change-password-webpage/
https://gist.github.com/mattrude/657334

How to Install and Configure 389 LDAP Directory Server on CentOS 6.4

389389 Directory Server is an enterprise-class open source Lightweight Directory Access Protocol (LDAP) server for Linux and based on Fedora Directory Server. 389 Directory server has been developed by Red Hat, as part of Red Hat’s community-supported Fedora Project. This steps has been tested on CentOS 6.4 x86_64 and may work on other version of CentOS as well.

1. Prepare EPEL repository.

2. Install 389-ds file :

[root@centos64 ~]# yum install 389-ds -y

3. Enable SELINUX :

[root@centos64 ~]# sestatus
SELinux status:                 enabled
SELinuxfs mount:                /selinux
Current mode:                   enforcing
Mode from config file:          enforcing
Policy version:                 24
Policy from config file:        targeted

4. Configure hostname, FQDN and host file has been configured correctly :

[root@centos64 ~]# hostname
centos64.ehowstuff.local
[root@centos64 ~]# cat /etc/hosts
127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
::1         localhost localhost.localdomain localhost6 localhost6.localdomain6

192.168.2.64    centos64.ehowstuff.local centos64

5. To install 389 LDAP, run the configuration script :

[root@centos64 ~]# /usr/sbin/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]:

==============================================================================
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 23-FEBRUARY-2012.

NOTICE : System is x86_64-unknown-linux2.6.32-358.2.1.el6.x86_64 (2 processors).

NOTICE : The net.ipv4.tcp_keepalive_time is set to 7200000 milliseconds
(120 minutes).  This may cause temporary server congestion from lost
client connections.

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

WARNING  : The warning messages above should be reviewed before proceeding.

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 [centos64.ehowstuff.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 [ehowstuff.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 [centos64]:

==============================================================================
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=ehowstuff, 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 'centos64' 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/setupDJucbG.log'

6. Start dirsrv and dirsrv-admin service :

[root@centos64 ~]# /etc/init.d/dirsrv start
Starting dirsrv:
    centos64...                                            [  OK  ]
[root@centos64 ~]# /etc/init.d/dirsrv-admin start
Starting dirsrv-admin:
                                                           [  OK  ]

7. Make dirsrv and dirsrv-admin service auto start at boot :

[root@centos64 ~]# chkconfig dirsrv on
[root@centos64 ~]# chkconfig dirsrv-admin on

8. Check dirsrv and dirsrv-admin service status :

[root@centos64 ~]# /etc/init.d/dirsrv-admin status
dirsrv-admin (pid 1409) is running...
[root@centos64 ~]# /etc/init.d/dirsrv status
dirsrv centos64 (pid 1317) is running...

How to Increase File Descriptors for 389 Directory Server

389This post will share with you on how to increase file descriptor on 389 Directory Server. The steps should be similar either in CentOS or Redhat Enterprise server. 389 Directory Server is an enterprise-class open source LDAP server for Linux. It is based on Fedora Directory Server.

1. Edit the /etc/sysconfig/dirsrv file and add the following line :

ulimit -n 8192

2. Increase nsslapd-maxdescriptors value. Assumed that directory instance was configured as slapd-centos62 :

[root@ldap ~]# vi /etc/dirsrv/slapd-centos62/dse.ldif

Add the following :

nsslapd-maxdescriptors: 8192

3. Restart dirsrv service to apply changes :

[root@ldap ~]# service dirsrv stop
Shutting down dirsrv:
    centos62...                                            [  OK  ]
[root@ldap ~]# service dirsrv start
Starting dirsrv:
    centos62...                                            [  OK  ]

How to Tuning, Install and Configure 389 Directory Server on CentOS 6.2

389

389 Directory Server

1.0 Tuning 389 Directory Server on CentOS 6.2

This post will share with you on how to perform system tuning analysis, install and configure 389 Directory Server on linux CentOS 6.2 server. 389 Directory Server is an enterprise-class open source LDAP server for Linux. It is based on Fedora Directory Server. This post assumed that your CentOS server has been completely setup EPEL repository.

Before start to configure the 389 Directory Server, it is better to adjust some performance and security settings. Follow the following steps to tuning the 389 Directory Server on CentOS 6.2.

1.1 Perform TCP Tuning on 389 Directory :

a) Decrease the time default value for tcp_keepalive_time connection. Edit the /etc/sysctl.conf file and add the following lines to the bottom of sysctl.conf.

[root@centos62 ~]# vi /etc/sysctl.conf
#Decrease the time default value for tcp_keepalive_time connection
net.ipv4.tcp_keepalive_time = 300

b) Increase number of local system ports available by editing this parameter in the /etc/sysctl.conf file :

[root@centos62 ~]# echo "net.ipv4.ip_local_port_range = 1024 65000" >> /etc/sysctl.conf

Show changes :

[root@centos62 ~]# cat /etc/sysctl.conf | grep net.ipv4.ip_local_port_range
net.ipv4.ip_local_port_range = 1024 65000

1.2 Perform File Tuning :

a) Increase the file descriptors by running these commands:

[root@centos62 ~]# echo "64000" > /proc/sys/fs/file-max

Show changes :

[root@centos62 ~]# cat /proc/sys/fs/file-max
64000

or
Simply run this command :

[root@centos62 ~]# echo "fs.file-max = 64000" >> /etc/sysctl.conf

Show changes :

[root@centos62 ~]# cat /etc/sysctl.conf | grep fs.file-max
fs.file-max = 64000

b) Edit /etc/profile as below :

[root@centos62 ~]# echo "ulimit -n 8192" >> /etc/profile

Show changes :

[root@centos62 ~]# cat /etc/profile | grep ulimit
ulimit -n 8192

c) Edit the file descriptors in /etc/security/limits.conf. Add two parameter at the bottom of the configuration file :

[root@centos62 ~]# vi /etc/security/limits.conf
# End of file
* soft nofile 524288
* hard nofile 524288

1.3 Directory Server Tuning :

a) Edit /etc/sysconfig/dirsrv and uncomment “ulimit -n 8192”

[root@centos62 ~]# cat /etc/sysconfig/dirsrv | grep ulimit
# hard limits are raised, then use ulimit - uncomment
# ulimit -n 8192

Edit as below :

[root@centos62 ~]# vi /etc/sysconfig/dirsrv
# In order to make more file descriptors available
# to the directory server, first make sure the system
# hard limits are raised, then use ulimit - uncomment
# out the following line and change the value to the
# desired value
ulimit -n 8192

1.4 Sufficient Memory Assigned :

Make sure you have assign or upgrade the physical memory to at least 1024MB.

2.0 Install 389 Directory Server on CentOS 6.2

This post will show you the quick steps to install 389 Directory Server on linux CentOS 6.2 server using EPEL repository. This post assumed that your CentOS server has been completely installed with minimum packages and the hostname and FQDN also has been configured correctly. Please make sure that you have configured EPEL repository on your CentOS 6.2 server.

Prerequisites :
How to Setup Local Yum Repository from CD-ROM/DVD-ROM image on CentOS 6.2
How to Install and Configure EPEL Repository on CentOS 6.2

2.1 Simply run this command to install 389 Directory Server on linux CentOS 6.2 server

[root@centos62 ~]# yum install 389-ds openldap-clients -y

Examples :

[root@centos62 ~]# yum install 389-ds openldap-clients -y
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
 * base: centos.ipserverone.com
 * epel: ftp.cuhk.edu.hk
 * extras: centos.ipserverone.com
 * updates: centos.ipserverone.com
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package 389-ds.noarch 0:1.2.2-1.el6 will be installed
--> Processing Dependency: 389-ds-console for package: 389-ds-1.2.2-1.el6.noarch
--> Processing Dependency: 389-ds-console-doc for package: 389-ds-1.2.2-1.el6.noarch
--> Processing Dependency: 389-admin-console-doc for package: 389-ds-1.2.2-1.el6.noarch
--> Processing Dependency: 389-ds-base for package: 389-ds-1.2.2-1.el6.noarch
--> Processing Dependency: 389-admin-console for package: 389-ds-1.2.2-1.el6.noarch
--> Processing Dependency: 389-admin for package: 389-ds-1.2.2-1.el6.noarch
--> Processing Dependency: idm-console-framework for package: 389-ds-1.2.2-1.el6.noarch
--> Processing Dependency: 389-dsgw for package: 389-ds-1.2.2-1.el6.noarch
--> Processing Dependency: 389-console for package: 389-ds-1.2.2-1.el6.noarch
---> Package openldap-clients.i686 0:2.4.23-20.el6 will be installed
--> Running transaction check
---> Package 389-admin.i686 0:1.1.25-1.el6 will be installed
--> Processing Dependency: perl-Mozilla-LDAP for package: 389-admin-1.1.25-1.el6.i686
--> Processing Dependency: nss-tools for package: 389-admin-1.1.25-1.el6.i686
--> Processing Dependency: policycoreutils-python for package: 389-admin-1.1.25-1.el6.i686
--> Processing Dependency: libicudata.so.42 for package: 389-admin-1.1.25-1.el6.i686
--> Processing Dependency: perl(Mozilla::LDAP::API) for package: 389-admin-1.1.25-1.el6.i686
--> Processing Dependency: perl(CGI) for package: 389-admin-1.1.25-1.el6.i686
--> Processing Dependency: libadminutil.so.0 for package: 389-admin-1.1.25-1.el6.i686
--> Processing Dependency: libadmsslutil.so.0 for package: 389-admin-1.1.25-1.el6.i686
--> Processing Dependency: perl(Mozilla::LDAP::Conn) for package: 389-admin-1.1.25-1.el6.i686
--> Processing Dependency: perl(Mozilla::LDAP::Utils) for package: 389-admin-1.1.25-1.el6.i686
--> Processing Dependency: libicui18n.so.42 for package: 389-admin-1.1.25-1.el6.i686
--> Processing Dependency: mod_nss for package: 389-admin-1.1.25-1.el6.i686
--> Processing Dependency: libicuuc.so.42 for package: 389-admin-1.1.25-1.el6.i686
---> Package 389-admin-console.noarch 0:1.1.8-1.el6 will be installed
---> Package 389-admin-console-doc.noarch 0:1.1.8-1.el6 will be installed
---> Package 389-console.noarch 0:1.1.7-1.el6 will be installed
--> Processing Dependency: java >= 1:1.6.0 for package: 389-console-1.1.7-1.el6.noarch
--> Processing Dependency: jpackage-utils for package: 389-console-1.1.7-1.el6.noarch
---> Package 389-ds-base.i686 0:1.2.9.14-1.el6_2.2 will be installed
--> Processing Dependency: 389-ds-base-libs = 1.2.9.14-1.el6_2.2 for package: 389-ds-base-1.2.9.14-1.el6_2.2.i686
--> Processing Dependency: cyrus-sasl-md5 for package: 389-ds-base-1.2.9.14-1.el6_2.2.i686
--> Processing Dependency: libnetsnmpmibs.so.20 for package: 389-ds-base-1.2.9.14-1.el6_2.2.i686
--> Processing Dependency: cyrus-sasl-gssapi for package: 389-ds-base-1.2.9.14-1.el6_2.2.i686
--> Processing Dependency: libnetsnmphelpers.so.20 for package: 389-ds-base-1.2.9.14-1.el6_2.2.i686
--> Processing Dependency: libnetsnmpagent.so.20 for package: 389-ds-base-1.2.9.14-1.el6_2.2.i686
--> Processing Dependency: libnetsnmp.so.20 for package: 389-ds-base-1.2.9.14-1.el6_2.2.i686
--> Processing Dependency: libslapd.so.0 for package: 389-ds-base-1.2.9.14-1.el6_2.2.i686
--> Processing Dependency: libsvrcore.so.0 for package: 389-ds-base-1.2.9.14-1.el6_2.2.i686
---> Package 389-ds-console.noarch 0:1.2.6-1.el6 will be installed
---> Package 389-ds-console-doc.noarch 0:1.2.6-1.el6 will be installed
---> Package 389-dsgw.i686 0:1.1.7-2.el6 will be installed
---> Package idm-console-framework.noarch 0:1.1.7-2.el6 will be installed
--> Processing Dependency: jss >= 4.2 for package: idm-console-framework-1.1.7-2.el6.noarch
--> Processing Dependency: ldapjdk for package: idm-console-framework-1.1.7-2.el6.noarch
--> Running transaction check
---> Package 389-adminutil.i686 0:1.1.14-2.el6 will be installed
---> Package 389-ds-base-libs.i686 0:1.2.9.14-1.el6_2.2 will be installed
---> Package cyrus-sasl-gssapi.i686 0:2.1.23-13.el6 will be installed
---> Package cyrus-sasl-md5.i686 0:2.1.23-13.el6 will be installed
---> Package java-1.6.0-openjdk.i686 1:1.6.0.0-1.43.1.10.6.el6_2 will be installed
--> Processing Dependency: tzdata-java for package: 1:java-1.6.0-openjdk-1.6.0.0-1.43.1.10.6.el6_2.i686
--> Processing Dependency: rhino for package: 1:java-1.6.0-openjdk-1.6.0.0-1.43.1.10.6.el6_2.i686
--> Processing Dependency: libgif.so.4 for package: 1:java-1.6.0-openjdk-1.6.0.0-1.43.1.10.6.el6_2.i686
---> Package jpackage-utils.noarch 0:1.7.5-3.12.el6 will be installed
---> Package jss.i686 0:4.2.6-20.el6 will be installed
---> Package ldapjdk.i686 0:4.18-6.el6 will be installed
--> Processing Dependency: libgcj_bc.so.1 for package: ldapjdk-4.18-6.el6.i686
--> Processing Dependency: java-gcj-compat for package: ldapjdk-4.18-6.el6.i686
--> Processing Dependency: java-gcj-compat for package: ldapjdk-4.18-6.el6.i686
---> Package libicu.i686 0:4.2.1-9.1.el6_2 will be installed
---> Package mod_nss.i686 0:1.0.8-13.el6 will be installed
---> Package net-snmp-libs.i686 1:5.5-37.el6_2.1 will be installed
--> Processing Dependency: libsensors.so.4 for package: 1:net-snmp-libs-5.5-37.el6_2.1.i686
---> Package nss-tools.i686 0:3.13.1-7.el6_2 will be installed
--> Processing Dependency: nss = 3.13.1-7.el6_2 for package: nss-tools-3.13.1-7.el6_2.i686
--> Processing Dependency: libnssutil3.so(NSSUTIL_3.13) for package: nss-tools-3.13.1-7.el6_2.i686
--> Processing Dependency: libnss3.so(NSS_3.13) for package: nss-tools-3.13.1-7.el6_2.i686
---> Package perl-CGI.i686 0:3.51-119.el6_1.1 will be installed
---> Package perl-Mozilla-LDAP.i686 0:1.5.3-4.el6 will be installed
---> Package policycoreutils-python.i686 0:2.0.83-19.21.el6_2 will be installed
--> Processing Dependency: policycoreutils = 2.0.83-19.21.el6_2 for package: policycoreutils-python-2.0.83-19.21.el6_2.i686
--> Processing Dependency: audit-libs-python >= 1.4.2-1 for package: policycoreutils-python-2.0.83-19.21.el6_2.i686
--> Processing Dependency: libsemanage-python >= 2.0.43-4 for package: policycoreutils-python-2.0.83-19.21.el6_2.i686
--> Processing Dependency: setools-libs-python for package: policycoreutils-python-2.0.83-19.21.el6_2.i686
--> Processing Dependency: libcgroup for package: policycoreutils-python-2.0.83-19.21.el6_2.i686
---> Package svrcore.i686 0:4.0.4-5.1.el6 will be installed
--> Running transaction check
---> Package audit-libs-python.i686 0:2.1.3-3.el6 will be installed
---> Package giflib.i686 0:4.1.6-3.1.el6 will be installed
---> Package java-1.5.0-gcj.i686 0:1.5.0.0-29.1.el6 will be installed
--> Processing Dependency: sinjdoc for package: java-1.5.0-gcj-1.5.0.0-29.1.el6.i686
---> Package libcgroup.i686 0:0.37-3.el6 will be installed
---> Package libgcj.i686 0:4.4.6-3.el6 will be installed
--> Processing Dependency: zip >= 2.1 for package: libgcj-4.4.6-3.el6.i686
---> Package libsemanage-python.i686 0:2.0.43-4.1.el6 will be installed
---> Package lm_sensors-libs.i686 0:3.1.1-10.el6 will be installed
---> Package nss.i686 0:3.12.10-17.el6_2 will be updated
--> Processing Dependency: nss = 3.12.10-17.el6_2 for package: nss-sysinit-3.12.10-17.el6_2.i686
---> Package nss.i686 0:3.13.1-7.el6_2 will be an update
--> Processing Dependency: nspr >= 4.8.9 for package: nss-3.13.1-7.el6_2.i686
---> Package nss-util.i686 0:3.12.10-2.el6 will be updated
---> Package nss-util.i686 0:3.13.1-3.el6_2 will be an update
---> Package policycoreutils.i686 0:2.0.83-19.18.el6 will be updated
---> Package policycoreutils.i686 0:2.0.83-19.21.el6_2 will be an update
---> Package rhino.noarch 0:1.7-0.7.r2.2.el6 will be installed
--> Processing Dependency: jline for package: rhino-1.7-0.7.r2.2.el6.noarch
---> Package setools-libs-python.i686 0:3.3.7-4.el6 will be installed
--> Processing Dependency: setools-libs = 3.3.7-4.el6 for package: setools-libs-python-3.3.7-4.el6.i686
--> Processing Dependency: libapol.so.4 for package: setools-libs-python-3.3.7-4.el6.i686
--> Processing Dependency: libsefs.so.4 for package: setools-libs-python-3.3.7-4.el6.i686
--> Processing Dependency: libpoldiff.so.1 for package: setools-libs-python-3.3.7-4.el6.i686
--> Processing Dependency: libseaudit.so.4(VERS_4.2) for package: setools-libs-python-3.3.7-4.el6.i686
--> Processing Dependency: libseaudit.so.4 for package: setools-libs-python-3.3.7-4.el6.i686
--> Processing Dependency: libapol.so.4(VERS_4.0) for package: setools-libs-python-3.3.7-4.el6.i686
--> Processing Dependency: libqpol.so.1(VERS_1.3) for package: setools-libs-python-3.3.7-4.el6.i686
--> Processing Dependency: libqpol.so.1 for package: setools-libs-python-3.3.7-4.el6.i686
--> Processing Dependency: libsefs.so.4(VERS_4.0) for package: setools-libs-python-3.3.7-4.el6.i686
--> Processing Dependency: libpoldiff.so.1(VERS_1.3) for package: setools-libs-python-3.3.7-4.el6.i686
--> Processing Dependency: libapol.so.4(VERS_4.1) for package: setools-libs-python-3.3.7-4.el6.i686
--> Processing Dependency: libqpol.so.1(VERS_1.4) for package: setools-libs-python-3.3.7-4.el6.i686
--> Processing Dependency: libseaudit.so.4(VERS_4.1) for package: setools-libs-python-3.3.7-4.el6.i686
--> Processing Dependency: libpoldiff.so.1(VERS_1.2) for package: setools-libs-python-3.3.7-4.el6.i686
--> Processing Dependency: libqpol.so.1(VERS_1.2) for package: setools-libs-python-3.3.7-4.el6.i686
---> Package tzdata-java.noarch 0:2011n-2.el6 will be installed
--> Running transaction check
---> Package jline.noarch 0:0.9.94-0.8.el6 will be installed
---> Package nspr.i686 0:4.8.8-3.el6 will be updated
---> Package nspr.i686 0:4.8.9-3.el6_2 will be an update
---> Package nss-sysinit.i686 0:3.12.10-17.el6_2 will be updated
---> Package nss-sysinit.i686 0:3.13.1-7.el6_2 will be an update
---> Package setools-libs.i686 0:3.3.7-4.el6 will be installed
---> Package sinjdoc.i686 0:0.5-9.1.el6 will be installed
--> Processing Dependency: java_cup >= 0.10 for package: sinjdoc-0.5-9.1.el6.i686
---> Package zip.i686 0:3.0-1.el6 will be installed
--> Running transaction check
---> Package java_cup.i686 1:0.10k-5.el6 will be installed
--> Finished Dependency Resolution

Dependencies Resolved

====================================================================================================
 Package                   Arch      Version                          Repository               Size
====================================================================================================
Installing:
 389-ds                    noarch    1.2.2-1.el6                      epel                    9.9 k
 openldap-clients          i686      2.4.23-20.el6                    CentOS6.2-Repository    155 k
Installing for dependencies:
 389-admin                 i686      1.1.25-1.el6                     epel                    341 k
 389-admin-console         noarch    1.1.8-1.el6                      epel                    202 k
 389-admin-console-doc     noarch    1.1.8-1.el6                      epel                     43 k
 389-adminutil             i686      1.1.14-2.el6                     epel                     64 k
 389-console               noarch    1.1.7-1.el6                      epel                     72 k
 389-ds-base               i686      1.2.9.14-1.el6_2.2               updates                 1.4 M
 389-ds-base-libs          i686      1.2.9.14-1.el6_2.2               updates                 369 k
 389-ds-console            noarch    1.2.6-1.el6                      epel                    1.4 M
 389-ds-console-doc        noarch    1.2.6-1.el6                      epel                     55 k
 389-dsgw                  i686      1.1.7-2.el6                      epel                    460 k
 audit-libs-python         i686      2.1.3-3.el6                      CentOS6.2-Repository     56 k
 cyrus-sasl-gssapi         i686      2.1.23-13.el6                    CentOS6.2-Repository     33 k
 cyrus-sasl-md5            i686      2.1.23-13.el6                    CentOS6.2-Repository     46 k
 giflib                    i686      4.1.6-3.1.el6                    CentOS6.2-Repository     37 k
 idm-console-framework     noarch    1.1.7-2.el6                      epel                    1.1 M
 java-1.5.0-gcj            i686      1.5.0.0-29.1.el6                 CentOS6.2-Repository    138 k
 java-1.6.0-openjdk        i686      1:1.6.0.0-1.43.1.10.6.el6_2      updates                  26 M
 java_cup                  i686      1:0.10k-5.el6                    CentOS6.2-Repository    178 k
 jline                     noarch    0.9.94-0.8.el6                   CentOS6.2-Repository     86 k
 jpackage-utils            noarch    1.7.5-3.12.el6                   CentOS6.2-Repository     59 k
 jss                       i686      4.2.6-20.el6                     CentOS6.2-Repository    745 k
 ldapjdk                   i686      4.18-6.el6                       CentOS6.2-Repository    749 k
 libcgroup                 i686      0.37-3.el6                       CentOS6.2-Repository    102 k
 libgcj                    i686      4.4.6-3.el6                      CentOS6.2-Repository     17 M
 libicu                    i686      4.2.1-9.1.el6_2                  updates                 5.0 M
 libsemanage-python        i686      2.0.43-4.1.el6                   CentOS6.2-Repository     80 k
 lm_sensors-libs           i686      3.1.1-10.el6                     CentOS6.2-Repository     36 k
 mod_nss                   i686      1.0.8-13.el6                     CentOS6.2-Repository     82 k
 net-snmp-libs             i686      1:5.5-37.el6_2.1                 updates                 1.5 M
 nss-tools                 i686      3.13.1-7.el6_2                   updates                 741 k
 perl-CGI                  i686      3.51-119.el6_1.1                 CentOS6.2-Repository    206 k
 perl-Mozilla-LDAP         i686      1.5.3-4.el6                      CentOS6.2-Repository    161 k
 policycoreutils-python    i686      2.0.83-19.21.el6_2               updates                 338 k
 rhino                     noarch    1.7-0.7.r2.2.el6                 CentOS6.2-Repository    778 k
 setools-libs              i686      3.3.7-4.el6                      CentOS6.2-Repository    400 k
 setools-libs-python       i686      3.3.7-4.el6                      CentOS6.2-Repository    210 k
 sinjdoc                   i686      0.5-9.1.el6                      CentOS6.2-Repository    646 k
 svrcore                   i686      4.0.4-5.1.el6                    CentOS6.2-Repository     15 k
 tzdata-java               noarch    2011n-2.el6                      updates                 153 k
 zip                       i686      3.0-1.el6                        CentOS6.2-Repository    252 k
Updating for dependencies:
 nspr                      i686      4.8.9-3.el6_2                    updates                 113 k
 nss                       i686      3.13.1-7.el6_2                   updates                 763 k
 nss-sysinit               i686      3.13.1-7.el6_2                   updates                  30 k
 nss-util                  i686      3.13.1-3.el6_2                   updates                  52 k
 policycoreutils           i686      2.0.83-19.21.el6_2               updates                 640 k

Transaction Summary
====================================================================================================
Install      42 Package(s)
Upgrade       5 Package(s)

Total download size: 63 M
Downloading Packages:
(1/47): 389-admin-1.1.25-1.el6.i686.rpm                                      | 341 kB     00:03
(2/47): 389-admin-console-1.1.8-1.el6.noarch.rpm                             | 202 kB     00:01
(3/47): 389-admin-console-doc-1.1.8-1.el6.noarch.rpm                         |  43 kB     00:00
(4/47): 389-adminutil-1.1.14-2.el6.i686.rpm                                  |  64 kB     00:00
(5/47): 389-console-1.1.7-1.el6.noarch.rpm                                   |  72 kB     00:00
(6/47): 389-ds-1.2.2-1.el6.noarch.rpm                                        | 9.9 kB     00:00
(7/47): 389-ds-base-1.2.9.14-1.el6_2.2.i686.rpm                              | 1.4 MB     00:11
(8/47): 389-ds-base-libs-1.2.9.14-1.el6_2.2.i686.rpm                         | 369 kB     00:03
(9/47): 389-ds-console-1.2.6-1.el6.noarch.rpm                                | 1.4 MB     00:13
(10/47): 389-ds-console-doc-1.2.6-1.el6.noarch.rpm                           |  55 kB     00:00
(11/47): 389-dsgw-1.1.7-2.el6.i686.rpm                                       | 460 kB     00:03
(12/47): idm-console-framework-1.1.7-2.el6.noarch.rpm                        | 1.1 MB     00:08
(13/47): java-1.6.0-openjdk-1.6.0.0-1.43.1.10.6.el6_2.i686.rpm               |  26 MB     03:56
(14/47): libicu-4.2.1-9.1.el6_2.i686.rpm                                     | 5.0 MB     00:44
(15/47): net-snmp-libs-5.5-37.el6_2.1.i686.rpm                               | 1.5 MB     00:13
(16/47): nspr-4.8.9-3.el6_2.i686.rpm                                         | 113 kB     00:00
(17/47): nss-3.13.1-7.el6_2.i686.rpm                                         | 763 kB     00:06
(18/47): nss-sysinit-3.13.1-7.el6_2.i686.rpm                                 |  30 kB     00:00
(19/47): nss-tools-3.13.1-7.el6_2.i686.rpm                                   | 741 kB     00:06
(20/47): nss-util-3.13.1-3.el6_2.i686.rpm                                    |  52 kB     00:00
(21/47): policycoreutils-2.0.83-19.21.el6_2.i686.rpm                         | 640 kB     00:05
(22/47): policycoreutils-python-2.0.83-19.21.el6_2.i686.rpm                  | 338 kB     00:03
(23/47): tzdata-java-2011n-2.el6.noarch.rpm                                  | 153 kB     00:01
----------------------------------------------------------------------------------------------------
Total                                                               174 kB/s |  63 MB     06:11
Running rpm_check_debug
Running Transaction Test
Transaction Test Succeeded
Running Transaction
  Installing : jpackage-utils-1.7.5-3.12.el6.noarch                                            1/52
  Installing : perl-CGI-3.51-119.el6_1.1.i686                                                  2/52
  Installing : jline-0.9.94-0.8.el6.noarch                                                     3/52
  Installing : rhino-1.7-0.7.r2.2.el6.noarch                                                   4/52
  Installing : tzdata-java-2011n-2.el6.noarch                                                  5/52
  Updating   : nspr-4.8.9-3.el6_2.i686                                                         6/52
  Updating   : nss-util-3.13.1-3.el6_2.i686                                                    7/52
  Updating   : nss-sysinit-3.13.1-7.el6_2.i686                                                 8/52
  Updating   : nss-3.13.1-7.el6_2.i686                                                         9/52
  Installing : libicu-4.2.1-9.1.el6_2.i686                                                    10/52
  Installing : perl-Mozilla-LDAP-1.5.3-4.el6.i686                                             11/52
  Installing : nss-tools-3.13.1-7.el6_2.i686                                                  12/52
  Installing : 389-adminutil-1.1.14-2.el6.i686                                                13/52
  Installing : svrcore-4.0.4-5.1.el6.i686                                                     14/52
  Updating   : policycoreutils-2.0.83-19.21.el6_2.i686                                        15/52
  Installing : 389-ds-base-libs-1.2.9.14-1.el6_2.2.i686                                       16/52
  Installing : mod_nss-1.0.8-13.el6.i686                                                      17/52
  Installing : openldap-clients-2.4.23-20.el6.i686                                            18/52
  Installing : lm_sensors-libs-3.1.1-10.el6.i686                                              19/52
  Installing : 1:net-snmp-libs-5.5-37.el6_2.1.i686                                            20/52
  Installing : giflib-4.1.6-3.1.el6.i686                                                      21/52
  Installing : zip-3.0-1.el6.i686                                                             22/52
  Installing : libgcj-4.4.6-3.el6.i686                                                        23/52
  Installing : 1:java-1.6.0-openjdk-1.6.0.0-1.43.1.10.6.el6_2.i686                            24/52
  Installing : java-1.5.0-gcj-1.5.0.0-29.1.el6.i686                                           25/52
  Installing : 1:java_cup-0.10k-5.el6.i686                                                    26/52
  Installing : sinjdoc-0.5-9.1.el6.i686                                                       27/52
  Installing : jss-4.2.6-20.el6.i686                                                          28/52
  Installing : ldapjdk-4.18-6.el6.i686                                                        29/52
  Installing : idm-console-framework-1.1.7-2.el6.noarch                                       30/52
  Installing : 389-console-1.1.7-1.el6.noarch                                                 31/52
  Installing : cyrus-sasl-gssapi-2.1.23-13.el6.i686                                           32/52
  Installing : setools-libs-3.3.7-4.el6.i686                                                  33/52
  Installing : setools-libs-python-3.3.7-4.el6.i686                                           34/52
  Installing : cyrus-sasl-md5-2.1.23-13.el6.i686                                              35/52
  Installing : libcgroup-0.37-3.el6.i686                                                      36/52
  Installing : audit-libs-python-2.1.3-3.el6.i686                                             37/52
  Installing : libsemanage-python-2.0.43-4.1.el6.i686                                         38/52
  Installing : policycoreutils-python-2.0.83-19.21.el6_2.i686                                 39/52
  Installing : 389-ds-base-1.2.9.14-1.el6_2.2.i686                                            40/52
  Installing : 389-admin-1.1.25-1.el6.i686                                                    41/52
  Installing : 389-admin-console-1.1.8-1.el6.noarch                                           42/52
  Installing : 389-ds-console-1.2.6-1.el6.noarch                                              43/52
  Installing : 389-ds-console-doc-1.2.6-1.el6.noarch                                          44/52
  Installing : 389-admin-console-doc-1.1.8-1.el6.noarch                                       45/52
  Installing : 389-dsgw-1.1.7-2.el6.i686                                                      46/52
  Installing : 389-ds-1.2.2-1.el6.noarch                                                      47/52
  Cleanup    : nss-sysinit-3.12.10-17.el6_2.i686                                              48/52
  Cleanup    : nss-3.12.10-17.el6_2.i686                                                      49/52
  Cleanup    : nss-util-3.12.10-2.el6.i686                                                    50/52
  Cleanup    : nspr-4.8.8-3.el6.i686                                                          51/52
  Cleanup    : policycoreutils-2.0.83-19.18.el6.i686                                          52/52

Installed:
  389-ds.noarch 0:1.2.2-1.el6                 openldap-clients.i686 0:2.4.23-20.el6

Dependency Installed:
  389-admin.i686 0:1.1.25-1.el6                          389-admin-console.noarch 0:1.1.8-1.el6
  389-admin-console-doc.noarch 0:1.1.8-1.el6             389-adminutil.i686 0:1.1.14-2.el6
  389-console.noarch 0:1.1.7-1.el6                       389-ds-base.i686 0:1.2.9.14-1.el6_2.2
  389-ds-base-libs.i686 0:1.2.9.14-1.el6_2.2             389-ds-console.noarch 0:1.2.6-1.el6
  389-ds-console-doc.noarch 0:1.2.6-1.el6                389-dsgw.i686 0:1.1.7-2.el6
  audit-libs-python.i686 0:2.1.3-3.el6                   cyrus-sasl-gssapi.i686 0:2.1.23-13.el6
  cyrus-sasl-md5.i686 0:2.1.23-13.el6                    giflib.i686 0:4.1.6-3.1.el6
  idm-console-framework.noarch 0:1.1.7-2.el6             java-1.5.0-gcj.i686 0:1.5.0.0-29.1.el6
  java-1.6.0-openjdk.i686 1:1.6.0.0-1.43.1.10.6.el6_2    java_cup.i686 1:0.10k-5.el6
  jline.noarch 0:0.9.94-0.8.el6                          jpackage-utils.noarch 0:1.7.5-3.12.el6
  jss.i686 0:4.2.6-20.el6                                ldapjdk.i686 0:4.18-6.el6
  libcgroup.i686 0:0.37-3.el6                            libgcj.i686 0:4.4.6-3.el6
  libicu.i686 0:4.2.1-9.1.el6_2                          libsemanage-python.i686 0:2.0.43-4.1.el6
  lm_sensors-libs.i686 0:3.1.1-10.el6                    mod_nss.i686 0:1.0.8-13.el6
  net-snmp-libs.i686 1:5.5-37.el6_2.1                    nss-tools.i686 0:3.13.1-7.el6_2
  perl-CGI.i686 0:3.51-119.el6_1.1                       perl-Mozilla-LDAP.i686 0:1.5.3-4.el6
  policycoreutils-python.i686 0:2.0.83-19.21.el6_2       rhino.noarch 0:1.7-0.7.r2.2.el6
  setools-libs.i686 0:3.3.7-4.el6                        setools-libs-python.i686 0:3.3.7-4.el6
  sinjdoc.i686 0:0.5-9.1.el6                             svrcore.i686 0:4.0.4-5.1.el6
  tzdata-java.noarch 0:2011n-2.el6                       zip.i686 0:3.0-1.el6

Dependency Updated:
  nspr.i686 0:4.8.9-3.el6_2                              nss.i686 0:3.13.1-7.el6_2
  nss-sysinit.i686 0:3.13.1-7.el6_2                      nss-util.i686 0:3.13.1-3.el6_2
  policycoreutils.i686 0:2.0.83-19.21.el6_2

Complete!

3.0 Setup and Configure 389 Directory Server on CentOS 6.2

On previous post, i already shows you on how to tuning and install 389 Directory Server on linux CentOS 6.2 server using EPEL repository. Again, before proceed to setup and configure 389 Directory Server on linux CentOS 6.2 server, please make sure that the hostname and FQDN also has been configured correctly.

3.1 Run the configuration script:

[root@centos62 ~]# setup-ds-admin.pl

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.ehowstuff.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 [ehowstuff.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=ehowstuff, 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'

4.0 Start, Stop and Restart 389 Directory Server on CentOS 6.2

This post will guide you on how to start, stop, restart and check dirsrv status for 389 Directory Server on linux CentOS 6.2 server. This post assumed that you have already installed and properly configured the 389 Directory Server on CentOS 6.2.

4.1 Some of the dirsrv usage for 389 Directory Server :

Usage: /etc/init.d/dirsrv {start|stop|status|restart|condrestart} [instance-name]

4.2 How to start 389 Directory Server :

[root@centos62 ~]# /etc/init.d/dirsrv start
Starting dirsrv:
    centos62...                                            [  OK  ]

4.3 How to stop 389 Directory Server :

[root@centos62 ~]# /etc/init.d/dirsrv stop
Shutting down dirsrv:
    centos62...                                            [  OK  ]

4.4 How to restart 389 Directory Server :

[root@centos62 ~]# /etc/init.d/dirsrv restart
Shutting down dirsrv:
    centos62...                                            [  OK  ]

4.5 How to check the status 389 Directory Server :

[root@centos62 ~]# /etc/init.d/dirsrv status
dirsrv centos62 (pid 1296) is running...

5.0 Configure Iptables Firewall for 389 Directory Server on CentOS 6.2

I will show the ports that need to be by passed in iptables firewall in order to make 389 Directory server accessible and working perfectly. Before the Windows Console (installed 389 Console.msi) from client’ PC connecting to 389 administration server, there are 3 important ports has to opened from iptables firewall. This will allow linux administrator or LDAP administrator to perform LDAP server search query or linux administration’s task. There are three(3) ports that are normally should be opened on 389 Directory Server.

a) Port 389 (ldap)
b) Port 636 (ldaps – only if using TLS/SSL)
c) Admin server port (9830 by default)

5.1 Run netstat command to see opened port :

[root@centos62 ~]# netstat -plunt
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address               Foreign Address             State       PID/Program name
tcp        0      0 0.0.0.0:22                  0.0.0.0:*                   LISTEN      1105/sshd
tcp        0      0 127.0.0.1:5432              0.0.0.0:*                   LISTEN      1140/postmaster
tcp        0      0 0.0.0.0:9830                0.0.0.0:*                   LISTEN      1415/httpd.worker
tcp        0      0 :::22                       :::*                        LISTEN      1105/sshd
tcp        0      0 ::1:5432                    :::*                        LISTEN      1140/postmaster
tcp        0      0 :::389                      :::*                        LISTEN      1792/ns-slapd

5.2 Open the iptables firewall configuration file then enable port 389, 636 and 9830 go through iptables firewall :

[root@centos62 ~]# vi /etc/sysconfig/iptables

5.3 Add these three(3) lines:

 
-A INPUT -m state --state NEW -m tcp -p tcp --dport 389 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 636 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 9830 -j ACCEPT

5.4 Then restart the iptables firewall :

[root@centos62 ~]# service iptables restart

Hope this complete steps may help you to prepare, tuning, install and configure 389 directory on your linux server.

How to Install 389 Directory Server on CentOS 5.8

389 Directory Server is an enterprise-class open source LDAP server for Linux and it’s based on Fedora Directory Server.This post will show you the quick steps to install 389 Directory Server on linux CentOS 5.8 server using EPEL repository. This post assumed that your CentOS server has been completely installed with minimum packages and the hostname and FQDN also has been configured correctly. Please make sure that you have configured EPEL repository on your CentOS 5.8 server.

Prerequisites :
How to Setup Local Yum Repository from CD-ROM/DVD-ROM image on CentOS 5.8
How to Install and Configure EPEL Repository on CentOS 5.8

Simply run this command to install 389 Directory Server on linux CentOS 5.8 server :

[root@centos58 ~]# yum install 389-ds openldap-clients -y

Examples :

[root@centos58 ~]# yum install 389-ds openldap-clients -y
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
 * base: mirror.oscc.org.my
 * epel: madura.idrepo.or.id
 * extras: mirror.oscc.org.my
 * rpmforge: mirror.oscc.org.my
 * updates: mirror.oscc.org.my
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package 389-ds.noarch 0:1.2.1-1.el5 set to be updated
--> Processing Dependency: 389-ds-console for package: 389-ds
--> Processing Dependency: 389-ds-console-doc for package: 389-ds
--> Processing Dependency: 389-admin-console-doc for package: 389-ds
--> Processing Dependency: 389-ds-base for package: 389-ds
--> Processing Dependency: 389-admin-console for package: 389-ds
--> Processing Dependency: 389-admin for package: 389-ds
--> Processing Dependency: idm-console-framework for package: 389-ds
--> Processing Dependency: 389-dsgw for package: 389-ds
--> Processing Dependency: 389-console for package: 389-ds
---> Package openldap-clients.i386 0:2.3.43-25.el5 set to be updated
--> Running transaction check
---> Package 389-admin.i386 0:1.1.29-1.el5 set to be updated
--> Processing Dependency: perl-Mozilla-LDAP for package: 389-admin
--> Processing Dependency: perl(Mozilla::LDAP::Utils) for package: 389-admin
--> Processing Dependency: perl(Mozilla::LDAP::Conn) for package: 389-admin
--> Processing Dependency: perl(Mozilla::LDAP::API) for package: 389-admin
--> Processing Dependency: nss-tools for package: 389-admin
--> Processing Dependency: mod_nss for package: 389-admin
--> Processing Dependency: libssldap60.so for package: 389-admin
--> Processing Dependency: libprldap60.so for package: 389-admin
--> Processing Dependency: libldif60.so for package: 389-admin
--> Processing Dependency: libldap60.so for package: 389-admin
--> Processing Dependency: libadmsslutil.so.0 for package: 389-admin
--> Processing Dependency: libadminutil.so.0 for package: 389-admin
---> Package 389-admin-console.noarch 0:1.1.8-1.el5 set to be updated
---> Package 389-admin-console-doc.noarch 0:1.1.8-1.el5 set to be updated
---> Package 389-console.noarch 0:1.1.7-3.el5 set to be updated
--> Processing Dependency: java >= 1:1.6.0 for package: 389-console
--> Processing Dependency: jpackage-utils for package: 389-console
---> Package 389-ds-base.i386 0:1.2.9.9-1.el5 set to be updated
--> Processing Dependency: 389-ds-base-libs = 1.2.9.9-1.el5 for package: 389-ds-base
--> Processing Dependency: libslapd.so.0 for package: 389-ds-base
--> Processing Dependency: cyrus-sasl-gssapi for package: 389-ds-base
--> Processing Dependency: cyrus-sasl-md5 for package: 389-ds-base
--> Processing Dependency: libsvrcore.so.0 for package: 389-ds-base
--> Processing Dependency: db4-utils for package: 389-ds-base
--> Processing Dependency: mozldap-tools for package: 389-ds-base
---> Package 389-ds-console.noarch 0:1.2.6-1.el5 set to be updated
---> Package 389-ds-console-doc.noarch 0:1.2.6-1.el5 set to be updated
---> Package 389-dsgw.i386 0:1.1.9-1.el5 set to be updated
---> Package idm-console-framework.noarch 0:1.1.7-5.el5 set to be updated
--> Processing Dependency: jss >= 4.2 for package: idm-console-framework
--> Processing Dependency: ldapjdk for package: idm-console-framework
--> Running transaction check
---> Package 389-adminutil.i386 0:1.1.15-1.el5 set to be updated
---> Package 389-ds-base-libs.i386 0:1.2.9.9-1.el5 set to be updated
---> Package cyrus-sasl-gssapi.i386 0:2.1.22-5.el5_4.3 set to be updated
---> Package cyrus-sasl-md5.i386 0:2.1.22-5.el5_4.3 set to be updated
---> Package db4-utils.i386 0:4.3.29-10.el5_5.2 set to be updated
---> Package java-1.6.0-openjdk.i386 1:1.6.0.0-1.25.1.10.6.el5_8 set to be updated
--> Processing Dependency: libasound.so.2(ALSA_0.9.0rc4) for package: java-1.6.0-openjdk
--> Processing Dependency: libasound.so.2 for package: java-1.6.0-openjdk
--> Processing Dependency: libgif.so.4 for package: java-1.6.0-openjdk
--> Processing Dependency: libXtst.so.6 for package: java-1.6.0-openjdk
--> Processing Dependency: libasound.so.2(ALSA_0.9) for package: java-1.6.0-openjdk
--> Processing Dependency: tzdata-java for package: java-1.6.0-openjdk
---> Package jpackage-utils.noarch 0:1.7.3-1jpp.2.el5 set to be updated
---> Package jss.i386 0:4.2.6-6.el5.centos set to be updated
---> Package ldapjdk.i386 0:4.18-2jpp.3.el5 set to be updated
--> Processing Dependency: java-gcj-compat for package: ldapjdk
--> Processing Dependency: libgcj_bc.so.1 for package: ldapjdk
---> Package mod_nss.i386 0:1.0.8-4.el5_6.1 set to be updated
---> Package mozldap.i386 0:6.0.5-1.el5 set to be updated
---> Package mozldap-tools.i386 0:6.0.5-1.el5 set to be updated
---> Package nss-tools.i386 0:3.13.1-5.el5_8 set to be updated
--> Processing Dependency: nss = 3.13.1-5.el5_8 for package: nss-tools
--> Processing Dependency: libnssutil3.so(NSSUTIL_3.13) for package: nss-tools
--> Processing Dependency: libnss3.so(NSS_3.13) for package: nss-tools
---> Package perl-Mozilla-LDAP.i386 0:1.5.2-4.el5 set to be updated
---> Package svrcore.i386 0:4.0.4-3.el5 set to be updated
--> Running transaction check
---> Package alsa-lib.i386 0:1.0.17-1.el5 set to be updated
---> Package giflib.i386 0:4.1.3-7.3.3.el5 set to be updated
---> Package java-1.4.2-gcj-compat.i386 0:1.4.2.0-40jpp.115 set to be updated
base/filelists                                                               | 3.0 MB     00:27
epel/filelists_db                                                            | 4.7 MB     00:44
extras/filelists_db                                                          | 213 kB     00:01
rpmforge/filelists_db                                                        | 6.0 MB     00:57
updates/filelists_db                                                         | 1.2 MB     00:10
--> Processing Dependency: zip for package: java-1.4.2-gcj-compat
--> Processing Dependency: gjdoc for package: java-1.4.2-gcj-compat
---> Package libXtst.i386 0:1.0.1-3.1 set to be updated
---> Package libgcj.i386 0:4.1.2-52.el5_8.1 set to be updated
--> Processing Dependency: libart_lgpl >= 2.1.0 for package: libgcj
--> Processing Dependency: libICE.so.6 for package: libgcj
--> Processing Dependency: libSM.so.6 for package: libgcj
---> Package nss.i386 0:3.13.1-5.el5_8 set to be updated
--> Processing Dependency: nspr >= 4.8.9 for package: nss
---> Package tzdata-java.i386 0:2012b-3.el5 set to be updated
--> Running transaction check
---> Package gjdoc.i386 0:0.7.7-12.el5 set to be updated
--> Processing Dependency: antlr for package: gjdoc
---> Package libICE.i386 0:1.0.1-2.1 set to be updated
---> Package libSM.i386 0:1.0.1-3.1 set to be updated
---> Package libart_lgpl.i386 0:2.3.17-4 set to be updated
---> Package nspr.i386 0:4.8.9-1.el5_8 set to be updated
---> Package zip.i386 0:2.31-2.el5 set to be updated
--> Running transaction check
---> Package antlr.i386 0:2.7.6-4jpp.2 set to be updated
--> Finished Dependency Resolution

Dependencies Resolved

====================================================================================================
 Package                  Arch      Version                           Repository               Size
====================================================================================================
Installing:
 389-ds                   noarch    1.2.1-1.el5                       epel                    9.1 k
 openldap-clients         i386      2.3.43-25.el5                     CentOS5.8-Repository    218 k
Installing for dependencies:
 389-admin                i386      1.1.29-1.el5                      epel                    412 k
 389-admin-console        noarch    1.1.8-1.el5                       epel                    203 k
 389-admin-console-doc    noarch    1.1.8-1.el5                       epel                     40 k
 389-adminutil            i386      1.1.15-1.el5                      epel                     70 k
 389-console              noarch    1.1.7-3.el5                       epel                     72 k
 389-ds-base              i386      1.2.9.9-1.el5                     epel                    1.6 M
 389-ds-base-libs         i386      1.2.9.9-1.el5                     epel                    407 k
 389-ds-console           noarch    1.2.6-1.el5                       epel                    1.4 M
 389-ds-console-doc       noarch    1.2.6-1.el5                       epel                     55 k
 389-dsgw                 i386      1.1.9-1.el5                       epel                    1.1 M
 alsa-lib                 i386      1.0.17-1.el5                      base                    412 k
 antlr                    i386      2.7.6-4jpp.2                      base                    978 k
 cyrus-sasl-gssapi        i386      2.1.22-5.el5_4.3                  base                     29 k
 cyrus-sasl-md5           i386      2.1.22-5.el5_4.3                  base                     46 k
 db4-utils                i386      4.3.29-10.el5_5.2                 base                    119 k
 giflib                   i386      4.1.3-7.3.3.el5                   base                     39 k
 gjdoc                    i386      0.7.7-12.el5                      base                    793 k
 idm-console-framework    noarch    1.1.7-5.el5                       epel                    1.1 M
 java-1.4.2-gcj-compat    i386      1.4.2.0-40jpp.115                 base                     29 k
 java-1.6.0-openjdk       i386      1:1.6.0.0-1.25.1.10.6.el5_8       updates                  37 M
 jpackage-utils           noarch    1.7.3-1jpp.2.el5                  base                     61 k
 jss                      i386      4.2.6-6.el5.centos                extras                  694 k
 ldapjdk                  i386      4.18-2jpp.3.el5                   base                    782 k
 libICE                   i386      1.0.1-2.1                         base                     54 k
 libSM                    i386      1.0.1-3.1                         base                     27 k
 libXtst                  i386      1.0.1-3.1                         base                     15 k
 libart_lgpl              i386      2.3.17-4                          base                     76 k
 libgcj                   i386      4.1.2-52.el5_8.1                  updates                  16 M
 mod_nss                  i386      1.0.8-4.el5_6.1                   base                     86 k
 mozldap                  i386      6.0.5-1.el5                       base                    132 k
 mozldap-tools            i386      6.0.5-1.el5                       base                    139 k
 nss-tools                i386      3.13.1-5.el5_8                    updates                 1.1 M
 perl-Mozilla-LDAP        i386      1.5.2-4.el5                       base                    181 k
 svrcore                  i386      4.0.4-3.el5                       base                     14 k
 tzdata-java              i386      2012b-3.el5                       updates                 181 k
 zip                      i386      2.31-2.el5                        base                    127 k
Updating for dependencies:
 nspr                     i386      4.8.9-1.el5_8                     updates                 121 k
 nss                      i386      3.13.1-5.el5_8                    updates                 1.1 M
.
.
.
.
  Updating       : nspr                                                                        1/42
  Updating       : nss                                                                         2/42
  Installing     : svrcore                                                                     3/42
  Installing     : mozldap                                                                     4/42
  Installing     : perl-Mozilla-LDAP                                                           5/42
  Installing     : nss-tools                                                                   6/42
  Installing     : 389-adminutil                                                               7/42
  Installing     : zip                                                                         8/42
  Installing     : libICE                                                                      9/42
  Installing     : libXtst                                                                    10/42
  Installing     : alsa-lib                                                                   11/42
  Installing     : libSM                                                                      12/42
  Installing     : mod_nss                                                                    13/42
  Installing     : mozldap-tools                                                              14/42
  Installing     : 389-ds-base-libs                                                           15/42
  Installing     : db4-utils                                                                  16/42
  Installing     : cyrus-sasl-md5                                                             17/42
  Installing     : giflib                                                                     18/42
  Installing     : cyrus-sasl-gssapi                                                          19/42
  Installing     : 389-ds-base                                                                20/42
  Installing     : 389-admin                                                                  21/42
  Installing     : 389-dsgw                                                                   22/42
  Installing     : libart_lgpl                                                                23/42
  Installing     : libgcj                                                                     24/42
  Installing     : openldap-clients                                                           25/42
  Installing     : jpackage-utils                                                             26/42
  Installing     : 389-ds-console                                                             27/42
  Installing     : 389-admin-console                                                          28/42
  Installing     : 389-admin-console-doc                                                      29/42
  Installing     : 389-ds-console-doc                                                         30/42
  Installing     : tzdata-java                                                                31/42
  Installing     : java-1.6.0-openjdk                                                         32/42
  Installing     : jss                                                                        33/42
  Installing     : java-1.4.2-gcj-compat                                                      34/42
  Installing     : ldapjdk                                                                    35/42
  Installing     : gjdoc                                                                      36/42
  Installing     : antlr                                                                      37/42
  Installing     : idm-console-framework                                                      38/42
  Installing     : 389-console                                                                39/42
  Installing     : 389-ds                                                                     40/42
  Cleanup        : nspr                                                                       41/42
  Cleanup        : nss                                                                        42/42

How to Tuning 389 Directory Server on CentOS 5.8

389 Directory Server is an enterprise-class open source LDAP server for Linux and it’s based on Fedora Directory Server. I will share with you on how to perform system tuning analysis for 389 Directory Server on linux CentOS 5.8 server. This post assumed that your CentOS server has been completely installed 389 Directory Server using EPEL repository. It is better to adjust some of the performance and security settings before we start to install 389 directory server. Follow this steps to tuning the 389 Directory Server on CentOS 5.8.

1. Perform TCP Tuning :

a) Decrease the time default value for tcp_keepalive_time connection. Edit the /etc/sysctl.conf file and add the following lines to the bottom of sysctl.conf.

[root@centos58 ~]# echo "net.ipv4.tcp_keepalive_time = 300" >> /etc/sysctl.conf

b) Increase number of local system ports available by editing this parameter in the /etc/sysctl.conf file :

[root@centos58 ~]# echo "net.ipv4.ip_local_port_range = 1024 65000" >> /etc/sysctl.conf

2. Perform File Tuning :

a) Increase the file descriptors by running these commands :

[root@centos58 ~]# echo "64000" > /proc/sys/fs/file-max

or
Simply run this command :

[root@centos58 ~]# echo "fs.file-max = 64000" >> /etc/sysctl.conf

b) Edit /etc/profile as below :

[root@centos58 ~]# echo "ulimit -n 8192" >> /etc/profile

c) Edit the file descriptors in /etc/security/limits.conf. Add two parameter at the bottom of the configuration file :

[root@centos58 ~]# echo "* soft nofile 524288" >> /etc/security/limits.conf
[root@centos58 ~]# echo "* hard nofile 524288" >> /etc/security/limits.conf

3. Directory Server Tuning :

[root@centos58 ~]# ulimit -n 8192

4. Sufficient Memory Assigned :
Make sure you have assign or upgrade the physical memory to at least 1024MB.

How to Install 389 Directory Server on CentOS 6.2

This post will show you the quick steps to install 389 Directory Server on linux CentOS 6.2 server using EPEL repository. 389 Directory Server is an enterprise-class open source LDAP server for Linux. It is based on Fedora Directory Server. This post assumed that your CentOS server has been completely installed with minimum packages and the hostname and FQDN also has been configured correctly. Please make sure that you have configured EPEL repository on your CentOS 6.2 server.

Prerequisites :
How to Setup Local Yum Repository from CD-ROM/DVD-ROM image on CentOS 6.2
How to Install and Configure EPEL Repository on CentOS 6.2

Simply run this command to install 389 Directory Server on linux CentOS 6.2 server :

[root@centos62 ~]# yum install 389-ds openldap-clients -y

Examples :

[root@centos62 ~]# yum install 389-ds openldap-clients -y
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
 * base: centos.ipserverone.com
 * epel: ftp.cuhk.edu.hk
 * extras: centos.ipserverone.com
 * updates: centos.ipserverone.com
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package 389-ds.noarch 0:1.2.2-1.el6 will be installed
--> Processing Dependency: 389-ds-console for package: 389-ds-1.2.2-1.el6.noarch
--> Processing Dependency: 389-ds-console-doc for package: 389-ds-1.2.2-1.el6.noarch
--> Processing Dependency: 389-admin-console-doc for package: 389-ds-1.2.2-1.el6.noarch
--> Processing Dependency: 389-ds-base for package: 389-ds-1.2.2-1.el6.noarch
--> Processing Dependency: 389-admin-console for package: 389-ds-1.2.2-1.el6.noarch
--> Processing Dependency: 389-admin for package: 389-ds-1.2.2-1.el6.noarch
--> Processing Dependency: idm-console-framework for package: 389-ds-1.2.2-1.el6.noarch
--> Processing Dependency: 389-dsgw for package: 389-ds-1.2.2-1.el6.noarch
--> Processing Dependency: 389-console for package: 389-ds-1.2.2-1.el6.noarch
---> Package openldap-clients.i686 0:2.4.23-20.el6 will be installed
--> Running transaction check
---> Package 389-admin.i686 0:1.1.25-1.el6 will be installed
--> Processing Dependency: perl-Mozilla-LDAP for package: 389-admin-1.1.25-1.el6.i686
--> Processing Dependency: nss-tools for package: 389-admin-1.1.25-1.el6.i686
--> Processing Dependency: policycoreutils-python for package: 389-admin-1.1.25-1.el6.i686
--> Processing Dependency: libicudata.so.42 for package: 389-admin-1.1.25-1.el6.i686
--> Processing Dependency: perl(Mozilla::LDAP::API) for package: 389-admin-1.1.25-1.el6.i686
--> Processing Dependency: perl(CGI) for package: 389-admin-1.1.25-1.el6.i686
--> Processing Dependency: libadminutil.so.0 for package: 389-admin-1.1.25-1.el6.i686
--> Processing Dependency: libadmsslutil.so.0 for package: 389-admin-1.1.25-1.el6.i686
--> Processing Dependency: perl(Mozilla::LDAP::Conn) for package: 389-admin-1.1.25-1.el6.i686
--> Processing Dependency: perl(Mozilla::LDAP::Utils) for package: 389-admin-1.1.25-1.el6.i686
--> Processing Dependency: libicui18n.so.42 for package: 389-admin-1.1.25-1.el6.i686
--> Processing Dependency: mod_nss for package: 389-admin-1.1.25-1.el6.i686
--> Processing Dependency: libicuuc.so.42 for package: 389-admin-1.1.25-1.el6.i686
---> Package 389-admin-console.noarch 0:1.1.8-1.el6 will be installed
---> Package 389-admin-console-doc.noarch 0:1.1.8-1.el6 will be installed
---> Package 389-console.noarch 0:1.1.7-1.el6 will be installed
--> Processing Dependency: java >= 1:1.6.0 for package: 389-console-1.1.7-1.el6.noarch
--> Processing Dependency: jpackage-utils for package: 389-console-1.1.7-1.el6.noarch
---> Package 389-ds-base.i686 0:1.2.9.14-1.el6_2.2 will be installed
--> Processing Dependency: 389-ds-base-libs = 1.2.9.14-1.el6_2.2 for package: 389-ds-base-1.2.9.14-1.el6_2.2.i686
--> Processing Dependency: cyrus-sasl-md5 for package: 389-ds-base-1.2.9.14-1.el6_2.2.i686
--> Processing Dependency: libnetsnmpmibs.so.20 for package: 389-ds-base-1.2.9.14-1.el6_2.2.i686
--> Processing Dependency: cyrus-sasl-gssapi for package: 389-ds-base-1.2.9.14-1.el6_2.2.i686
--> Processing Dependency: libnetsnmphelpers.so.20 for package: 389-ds-base-1.2.9.14-1.el6_2.2.i686
--> Processing Dependency: libnetsnmpagent.so.20 for package: 389-ds-base-1.2.9.14-1.el6_2.2.i686
--> Processing Dependency: libnetsnmp.so.20 for package: 389-ds-base-1.2.9.14-1.el6_2.2.i686
--> Processing Dependency: libslapd.so.0 for package: 389-ds-base-1.2.9.14-1.el6_2.2.i686
--> Processing Dependency: libsvrcore.so.0 for package: 389-ds-base-1.2.9.14-1.el6_2.2.i686
---> Package 389-ds-console.noarch 0:1.2.6-1.el6 will be installed
---> Package 389-ds-console-doc.noarch 0:1.2.6-1.el6 will be installed
---> Package 389-dsgw.i686 0:1.1.7-2.el6 will be installed
---> Package idm-console-framework.noarch 0:1.1.7-2.el6 will be installed
--> Processing Dependency: jss >= 4.2 for package: idm-console-framework-1.1.7-2.el6.noarch
--> Processing Dependency: ldapjdk for package: idm-console-framework-1.1.7-2.el6.noarch
--> Running transaction check
---> Package 389-adminutil.i686 0:1.1.14-2.el6 will be installed
---> Package 389-ds-base-libs.i686 0:1.2.9.14-1.el6_2.2 will be installed
---> Package cyrus-sasl-gssapi.i686 0:2.1.23-13.el6 will be installed
---> Package cyrus-sasl-md5.i686 0:2.1.23-13.el6 will be installed
---> Package java-1.6.0-openjdk.i686 1:1.6.0.0-1.43.1.10.6.el6_2 will be installed
--> Processing Dependency: tzdata-java for package: 1:java-1.6.0-openjdk-1.6.0.0-1.43.1.10.6.el6_2.i686
--> Processing Dependency: rhino for package: 1:java-1.6.0-openjdk-1.6.0.0-1.43.1.10.6.el6_2.i686
--> Processing Dependency: libgif.so.4 for package: 1:java-1.6.0-openjdk-1.6.0.0-1.43.1.10.6.el6_2.i686
---> Package jpackage-utils.noarch 0:1.7.5-3.12.el6 will be installed
---> Package jss.i686 0:4.2.6-20.el6 will be installed
---> Package ldapjdk.i686 0:4.18-6.el6 will be installed
--> Processing Dependency: libgcj_bc.so.1 for package: ldapjdk-4.18-6.el6.i686
--> Processing Dependency: java-gcj-compat for package: ldapjdk-4.18-6.el6.i686
--> Processing Dependency: java-gcj-compat for package: ldapjdk-4.18-6.el6.i686
---> Package libicu.i686 0:4.2.1-9.1.el6_2 will be installed
---> Package mod_nss.i686 0:1.0.8-13.el6 will be installed
---> Package net-snmp-libs.i686 1:5.5-37.el6_2.1 will be installed
--> Processing Dependency: libsensors.so.4 for package: 1:net-snmp-libs-5.5-37.el6_2.1.i686
---> Package nss-tools.i686 0:3.13.1-7.el6_2 will be installed
--> Processing Dependency: nss = 3.13.1-7.el6_2 for package: nss-tools-3.13.1-7.el6_2.i686
--> Processing Dependency: libnssutil3.so(NSSUTIL_3.13) for package: nss-tools-3.13.1-7.el6_2.i686
--> Processing Dependency: libnss3.so(NSS_3.13) for package: nss-tools-3.13.1-7.el6_2.i686
---> Package perl-CGI.i686 0:3.51-119.el6_1.1 will be installed
---> Package perl-Mozilla-LDAP.i686 0:1.5.3-4.el6 will be installed
---> Package policycoreutils-python.i686 0:2.0.83-19.21.el6_2 will be installed
--> Processing Dependency: policycoreutils = 2.0.83-19.21.el6_2 for package: policycoreutils-python-2.0.83-19.21.el6_2.i686
--> Processing Dependency: audit-libs-python >= 1.4.2-1 for package: policycoreutils-python-2.0.83-19.21.el6_2.i686
--> Processing Dependency: libsemanage-python >= 2.0.43-4 for package: policycoreutils-python-2.0.83-19.21.el6_2.i686
--> Processing Dependency: setools-libs-python for package: policycoreutils-python-2.0.83-19.21.el6_2.i686
--> Processing Dependency: libcgroup for package: policycoreutils-python-2.0.83-19.21.el6_2.i686
---> Package svrcore.i686 0:4.0.4-5.1.el6 will be installed
--> Running transaction check
---> Package audit-libs-python.i686 0:2.1.3-3.el6 will be installed
---> Package giflib.i686 0:4.1.6-3.1.el6 will be installed
---> Package java-1.5.0-gcj.i686 0:1.5.0.0-29.1.el6 will be installed
--> Processing Dependency: sinjdoc for package: java-1.5.0-gcj-1.5.0.0-29.1.el6.i686
---> Package libcgroup.i686 0:0.37-3.el6 will be installed
---> Package libgcj.i686 0:4.4.6-3.el6 will be installed
--> Processing Dependency: zip >= 2.1 for package: libgcj-4.4.6-3.el6.i686
---> Package libsemanage-python.i686 0:2.0.43-4.1.el6 will be installed
---> Package lm_sensors-libs.i686 0:3.1.1-10.el6 will be installed
---> Package nss.i686 0:3.12.10-17.el6_2 will be updated
--> Processing Dependency: nss = 3.12.10-17.el6_2 for package: nss-sysinit-3.12.10-17.el6_2.i686
---> Package nss.i686 0:3.13.1-7.el6_2 will be an update
--> Processing Dependency: nspr >= 4.8.9 for package: nss-3.13.1-7.el6_2.i686
---> Package nss-util.i686 0:3.12.10-2.el6 will be updated
---> Package nss-util.i686 0:3.13.1-3.el6_2 will be an update
---> Package policycoreutils.i686 0:2.0.83-19.18.el6 will be updated
---> Package policycoreutils.i686 0:2.0.83-19.21.el6_2 will be an update
---> Package rhino.noarch 0:1.7-0.7.r2.2.el6 will be installed
--> Processing Dependency: jline for package: rhino-1.7-0.7.r2.2.el6.noarch
---> Package setools-libs-python.i686 0:3.3.7-4.el6 will be installed
--> Processing Dependency: setools-libs = 3.3.7-4.el6 for package: setools-libs-python-3.3.7-4.el6.i686
--> Processing Dependency: libapol.so.4 for package: setools-libs-python-3.3.7-4.el6.i686
--> Processing Dependency: libsefs.so.4 for package: setools-libs-python-3.3.7-4.el6.i686
--> Processing Dependency: libpoldiff.so.1 for package: setools-libs-python-3.3.7-4.el6.i686
--> Processing Dependency: libseaudit.so.4(VERS_4.2) for package: setools-libs-python-3.3.7-4.el6.i686
--> Processing Dependency: libseaudit.so.4 for package: setools-libs-python-3.3.7-4.el6.i686
--> Processing Dependency: libapol.so.4(VERS_4.0) for package: setools-libs-python-3.3.7-4.el6.i686
--> Processing Dependency: libqpol.so.1(VERS_1.3) for package: setools-libs-python-3.3.7-4.el6.i686
--> Processing Dependency: libqpol.so.1 for package: setools-libs-python-3.3.7-4.el6.i686
--> Processing Dependency: libsefs.so.4(VERS_4.0) for package: setools-libs-python-3.3.7-4.el6.i686
--> Processing Dependency: libpoldiff.so.1(VERS_1.3) for package: setools-libs-python-3.3.7-4.el6.i686
--> Processing Dependency: libapol.so.4(VERS_4.1) for package: setools-libs-python-3.3.7-4.el6.i686
--> Processing Dependency: libqpol.so.1(VERS_1.4) for package: setools-libs-python-3.3.7-4.el6.i686
--> Processing Dependency: libseaudit.so.4(VERS_4.1) for package: setools-libs-python-3.3.7-4.el6.i686
--> Processing Dependency: libpoldiff.so.1(VERS_1.2) for package: setools-libs-python-3.3.7-4.el6.i686
--> Processing Dependency: libqpol.so.1(VERS_1.2) for package: setools-libs-python-3.3.7-4.el6.i686
---> Package tzdata-java.noarch 0:2011n-2.el6 will be installed
--> Running transaction check
---> Package jline.noarch 0:0.9.94-0.8.el6 will be installed
---> Package nspr.i686 0:4.8.8-3.el6 will be updated
---> Package nspr.i686 0:4.8.9-3.el6_2 will be an update
---> Package nss-sysinit.i686 0:3.12.10-17.el6_2 will be updated
---> Package nss-sysinit.i686 0:3.13.1-7.el6_2 will be an update
---> Package setools-libs.i686 0:3.3.7-4.el6 will be installed
---> Package sinjdoc.i686 0:0.5-9.1.el6 will be installed
--> Processing Dependency: java_cup >= 0.10 for package: sinjdoc-0.5-9.1.el6.i686
---> Package zip.i686 0:3.0-1.el6 will be installed
--> Running transaction check
---> Package java_cup.i686 1:0.10k-5.el6 will be installed
--> Finished Dependency Resolution

Dependencies Resolved

====================================================================================================
 Package                   Arch      Version                          Repository               Size
====================================================================================================
Installing:
 389-ds                    noarch    1.2.2-1.el6                      epel                    9.9 k
 openldap-clients          i686      2.4.23-20.el6                    CentOS6.2-Repository    155 k
Installing for dependencies:
 389-admin                 i686      1.1.25-1.el6                     epel                    341 k
 389-admin-console         noarch    1.1.8-1.el6                      epel                    202 k
 389-admin-console-doc     noarch    1.1.8-1.el6                      epel                     43 k
 389-adminutil             i686      1.1.14-2.el6                     epel                     64 k
 389-console               noarch    1.1.7-1.el6                      epel                     72 k
 389-ds-base               i686      1.2.9.14-1.el6_2.2               updates                 1.4 M
 389-ds-base-libs          i686      1.2.9.14-1.el6_2.2               updates                 369 k
 389-ds-console            noarch    1.2.6-1.el6                      epel                    1.4 M
 389-ds-console-doc        noarch    1.2.6-1.el6                      epel                     55 k
 389-dsgw                  i686      1.1.7-2.el6                      epel                    460 k
 audit-libs-python         i686      2.1.3-3.el6                      CentOS6.2-Repository     56 k
 cyrus-sasl-gssapi         i686      2.1.23-13.el6                    CentOS6.2-Repository     33 k
 cyrus-sasl-md5            i686      2.1.23-13.el6                    CentOS6.2-Repository     46 k
 giflib                    i686      4.1.6-3.1.el6                    CentOS6.2-Repository     37 k
 idm-console-framework     noarch    1.1.7-2.el6                      epel                    1.1 M
 java-1.5.0-gcj            i686      1.5.0.0-29.1.el6                 CentOS6.2-Repository    138 k
 java-1.6.0-openjdk        i686      1:1.6.0.0-1.43.1.10.6.el6_2      updates                  26 M
 java_cup                  i686      1:0.10k-5.el6                    CentOS6.2-Repository    178 k
 jline                     noarch    0.9.94-0.8.el6                   CentOS6.2-Repository     86 k
 jpackage-utils            noarch    1.7.5-3.12.el6                   CentOS6.2-Repository     59 k
 jss                       i686      4.2.6-20.el6                     CentOS6.2-Repository    745 k
 ldapjdk                   i686      4.18-6.el6                       CentOS6.2-Repository    749 k
 libcgroup                 i686      0.37-3.el6                       CentOS6.2-Repository    102 k
 libgcj                    i686      4.4.6-3.el6                      CentOS6.2-Repository     17 M
 libicu                    i686      4.2.1-9.1.el6_2                  updates                 5.0 M
 libsemanage-python        i686      2.0.43-4.1.el6                   CentOS6.2-Repository     80 k
 lm_sensors-libs           i686      3.1.1-10.el6                     CentOS6.2-Repository     36 k
 mod_nss                   i686      1.0.8-13.el6                     CentOS6.2-Repository     82 k
 net-snmp-libs             i686      1:5.5-37.el6_2.1                 updates                 1.5 M
 nss-tools                 i686      3.13.1-7.el6_2                   updates                 741 k
 perl-CGI                  i686      3.51-119.el6_1.1                 CentOS6.2-Repository    206 k
 perl-Mozilla-LDAP         i686      1.5.3-4.el6                      CentOS6.2-Repository    161 k
 policycoreutils-python    i686      2.0.83-19.21.el6_2               updates                 338 k
 rhino                     noarch    1.7-0.7.r2.2.el6                 CentOS6.2-Repository    778 k
 setools-libs              i686      3.3.7-4.el6                      CentOS6.2-Repository    400 k
 setools-libs-python       i686      3.3.7-4.el6                      CentOS6.2-Repository    210 k
 sinjdoc                   i686      0.5-9.1.el6                      CentOS6.2-Repository    646 k
 svrcore                   i686      4.0.4-5.1.el6                    CentOS6.2-Repository     15 k
 tzdata-java               noarch    2011n-2.el6                      updates                 153 k
 zip                       i686      3.0-1.el6                        CentOS6.2-Repository    252 k
Updating for dependencies:
 nspr                      i686      4.8.9-3.el6_2                    updates                 113 k
 nss                       i686      3.13.1-7.el6_2                   updates                 763 k
 nss-sysinit               i686      3.13.1-7.el6_2                   updates                  30 k
 nss-util                  i686      3.13.1-3.el6_2                   updates                  52 k
 policycoreutils           i686      2.0.83-19.21.el6_2               updates                 640 k

Transaction Summary
====================================================================================================
Install      42 Package(s)
Upgrade       5 Package(s)

Total download size: 63 M
Downloading Packages:
(1/47): 389-admin-1.1.25-1.el6.i686.rpm                                      | 341 kB     00:03
(2/47): 389-admin-console-1.1.8-1.el6.noarch.rpm                             | 202 kB     00:01
(3/47): 389-admin-console-doc-1.1.8-1.el6.noarch.rpm                         |  43 kB     00:00
(4/47): 389-adminutil-1.1.14-2.el6.i686.rpm                                  |  64 kB     00:00
(5/47): 389-console-1.1.7-1.el6.noarch.rpm                                   |  72 kB     00:00
(6/47): 389-ds-1.2.2-1.el6.noarch.rpm                                        | 9.9 kB     00:00
(7/47): 389-ds-base-1.2.9.14-1.el6_2.2.i686.rpm                              | 1.4 MB     00:11
(8/47): 389-ds-base-libs-1.2.9.14-1.el6_2.2.i686.rpm                         | 369 kB     00:03
(9/47): 389-ds-console-1.2.6-1.el6.noarch.rpm                                | 1.4 MB     00:13
(10/47): 389-ds-console-doc-1.2.6-1.el6.noarch.rpm                           |  55 kB     00:00
(11/47): 389-dsgw-1.1.7-2.el6.i686.rpm                                       | 460 kB     00:03
(12/47): idm-console-framework-1.1.7-2.el6.noarch.rpm                        | 1.1 MB     00:08
(13/47): java-1.6.0-openjdk-1.6.0.0-1.43.1.10.6.el6_2.i686.rpm               |  26 MB     03:56
(14/47): libicu-4.2.1-9.1.el6_2.i686.rpm                                     | 5.0 MB     00:44
(15/47): net-snmp-libs-5.5-37.el6_2.1.i686.rpm                               | 1.5 MB     00:13
(16/47): nspr-4.8.9-3.el6_2.i686.rpm                                         | 113 kB     00:00
(17/47): nss-3.13.1-7.el6_2.i686.rpm                                         | 763 kB     00:06
(18/47): nss-sysinit-3.13.1-7.el6_2.i686.rpm                                 |  30 kB     00:00
(19/47): nss-tools-3.13.1-7.el6_2.i686.rpm                                   | 741 kB     00:06
(20/47): nss-util-3.13.1-3.el6_2.i686.rpm                                    |  52 kB     00:00
(21/47): policycoreutils-2.0.83-19.21.el6_2.i686.rpm                         | 640 kB     00:05
(22/47): policycoreutils-python-2.0.83-19.21.el6_2.i686.rpm                  | 338 kB     00:03
(23/47): tzdata-java-2011n-2.el6.noarch.rpm                                  | 153 kB     00:01
----------------------------------------------------------------------------------------------------
Total                                                               174 kB/s |  63 MB     06:11
Running rpm_check_debug
Running Transaction Test
Transaction Test Succeeded
Running Transaction
  Installing : jpackage-utils-1.7.5-3.12.el6.noarch                                            1/52
  Installing : perl-CGI-3.51-119.el6_1.1.i686                                                  2/52
  Installing : jline-0.9.94-0.8.el6.noarch                                                     3/52
  Installing : rhino-1.7-0.7.r2.2.el6.noarch                                                   4/52
  Installing : tzdata-java-2011n-2.el6.noarch                                                  5/52
  Updating   : nspr-4.8.9-3.el6_2.i686                                                         6/52
  Updating   : nss-util-3.13.1-3.el6_2.i686                                                    7/52
  Updating   : nss-sysinit-3.13.1-7.el6_2.i686                                                 8/52
  Updating   : nss-3.13.1-7.el6_2.i686                                                         9/52
  Installing : libicu-4.2.1-9.1.el6_2.i686                                                    10/52
  Installing : perl-Mozilla-LDAP-1.5.3-4.el6.i686                                             11/52
  Installing : nss-tools-3.13.1-7.el6_2.i686                                                  12/52
  Installing : 389-adminutil-1.1.14-2.el6.i686                                                13/52
  Installing : svrcore-4.0.4-5.1.el6.i686                                                     14/52
  Updating   : policycoreutils-2.0.83-19.21.el6_2.i686                                        15/52
  Installing : 389-ds-base-libs-1.2.9.14-1.el6_2.2.i686                                       16/52
  Installing : mod_nss-1.0.8-13.el6.i686                                                      17/52
  Installing : openldap-clients-2.4.23-20.el6.i686                                            18/52
  Installing : lm_sensors-libs-3.1.1-10.el6.i686                                              19/52
  Installing : 1:net-snmp-libs-5.5-37.el6_2.1.i686                                            20/52
  Installing : giflib-4.1.6-3.1.el6.i686                                                      21/52
  Installing : zip-3.0-1.el6.i686                                                             22/52
  Installing : libgcj-4.4.6-3.el6.i686                                                        23/52
  Installing : 1:java-1.6.0-openjdk-1.6.0.0-1.43.1.10.6.el6_2.i686                            24/52
  Installing : java-1.5.0-gcj-1.5.0.0-29.1.el6.i686                                           25/52
  Installing : 1:java_cup-0.10k-5.el6.i686                                                    26/52
  Installing : sinjdoc-0.5-9.1.el6.i686                                                       27/52
  Installing : jss-4.2.6-20.el6.i686                                                          28/52
  Installing : ldapjdk-4.18-6.el6.i686                                                        29/52
  Installing : idm-console-framework-1.1.7-2.el6.noarch                                       30/52
  Installing : 389-console-1.1.7-1.el6.noarch                                                 31/52
  Installing : cyrus-sasl-gssapi-2.1.23-13.el6.i686                                           32/52
  Installing : setools-libs-3.3.7-4.el6.i686                                                  33/52
  Installing : setools-libs-python-3.3.7-4.el6.i686                                           34/52
  Installing : cyrus-sasl-md5-2.1.23-13.el6.i686                                              35/52
  Installing : libcgroup-0.37-3.el6.i686                                                      36/52
  Installing : audit-libs-python-2.1.3-3.el6.i686                                             37/52
  Installing : libsemanage-python-2.0.43-4.1.el6.i686                                         38/52
  Installing : policycoreutils-python-2.0.83-19.21.el6_2.i686                                 39/52
  Installing : 389-ds-base-1.2.9.14-1.el6_2.2.i686                                            40/52
  Installing : 389-admin-1.1.25-1.el6.i686                                                    41/52
  Installing : 389-admin-console-1.1.8-1.el6.noarch                                           42/52
  Installing : 389-ds-console-1.2.6-1.el6.noarch                                              43/52
  Installing : 389-ds-console-doc-1.2.6-1.el6.noarch                                          44/52
  Installing : 389-admin-console-doc-1.1.8-1.el6.noarch                                       45/52
  Installing : 389-dsgw-1.1.7-2.el6.i686                                                      46/52
  Installing : 389-ds-1.2.2-1.el6.noarch                                                      47/52
  Cleanup    : nss-sysinit-3.12.10-17.el6_2.i686                                              48/52
  Cleanup    : nss-3.12.10-17.el6_2.i686                                                      49/52
  Cleanup    : nss-util-3.12.10-2.el6.i686                                                    50/52
  Cleanup    : nspr-4.8.8-3.el6.i686                                                          51/52
  Cleanup    : policycoreutils-2.0.83-19.18.el6.i686                                          52/52

Installed:
  389-ds.noarch 0:1.2.2-1.el6                 openldap-clients.i686 0:2.4.23-20.el6

Dependency Installed:
  389-admin.i686 0:1.1.25-1.el6                          389-admin-console.noarch 0:1.1.8-1.el6
  389-admin-console-doc.noarch 0:1.1.8-1.el6             389-adminutil.i686 0:1.1.14-2.el6
  389-console.noarch 0:1.1.7-1.el6                       389-ds-base.i686 0:1.2.9.14-1.el6_2.2
  389-ds-base-libs.i686 0:1.2.9.14-1.el6_2.2             389-ds-console.noarch 0:1.2.6-1.el6
  389-ds-console-doc.noarch 0:1.2.6-1.el6                389-dsgw.i686 0:1.1.7-2.el6
  audit-libs-python.i686 0:2.1.3-3.el6                   cyrus-sasl-gssapi.i686 0:2.1.23-13.el6
  cyrus-sasl-md5.i686 0:2.1.23-13.el6                    giflib.i686 0:4.1.6-3.1.el6
  idm-console-framework.noarch 0:1.1.7-2.el6             java-1.5.0-gcj.i686 0:1.5.0.0-29.1.el6
  java-1.6.0-openjdk.i686 1:1.6.0.0-1.43.1.10.6.el6_2    java_cup.i686 1:0.10k-5.el6
  jline.noarch 0:0.9.94-0.8.el6                          jpackage-utils.noarch 0:1.7.5-3.12.el6
  jss.i686 0:4.2.6-20.el6                                ldapjdk.i686 0:4.18-6.el6
  libcgroup.i686 0:0.37-3.el6                            libgcj.i686 0:4.4.6-3.el6
  libicu.i686 0:4.2.1-9.1.el6_2                          libsemanage-python.i686 0:2.0.43-4.1.el6
  lm_sensors-libs.i686 0:3.1.1-10.el6                    mod_nss.i686 0:1.0.8-13.el6
  net-snmp-libs.i686 1:5.5-37.el6_2.1                    nss-tools.i686 0:3.13.1-7.el6_2
  perl-CGI.i686 0:3.51-119.el6_1.1                       perl-Mozilla-LDAP.i686 0:1.5.3-4.el6
  policycoreutils-python.i686 0:2.0.83-19.21.el6_2       rhino.noarch 0:1.7-0.7.r2.2.el6
  setools-libs.i686 0:3.3.7-4.el6                        setools-libs-python.i686 0:3.3.7-4.el6
  sinjdoc.i686 0:0.5-9.1.el6                             svrcore.i686 0:4.0.4-5.1.el6
  tzdata-java.noarch 0:2011n-2.el6                       zip.i686 0:3.0-1.el6

Dependency Updated:
  nspr.i686 0:4.8.9-3.el6_2                              nss.i686 0:3.13.1-7.el6_2
  nss-sysinit.i686 0:3.13.1-7.el6_2                      nss-util.i686 0:3.13.1-3.el6_2
  policycoreutils.i686 0:2.0.83-19.21.el6_2

Complete!

How to Setup and Configure 389 Directory Server on CentOS 6.2

On previous post(Install 389 Directory Server) shows you on how to install 389 Directory Server on linux CentOS 6.2 server using EPEL repository. 389 Directory Server is an enterprise-class open source LDAP server for Linux. It is based on Fedora Directory Server. Before proceed to setup and configure 389 Directory Server on linux CentOS 6.2 server, please make sure that the hostname and FQDN also has been configured correctly.

Run the configuration script :

[root@centos62 ~]# setup-ds-admin.pl

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.ehowstuff.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 [ehowstuff.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=ehowstuff, 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'

How to Install and Configure phpLDAPadmin on CentOS 6.2

phpLDAPadmin (also known as PLA) is a web-based LDAP administration tool to manage, browse and administer your LDAP directory server. Since it is a web application, this LDAP browser works on many platforms, making your LDAP server easily manageable from any location. With it you can browse your LDAP tree, view LDAP schema, perform searches, create, delete, copy and edit LDAP entries. You can even copy entries between servers. This post will show you on how to install phpLDAPadmin on linux CentOS 6.2 server. Assumed that you already install install EPEL repository on your CentOS 6.2 server as below :
How to Install and Configure EPEL Repository on CentOS 6.2

1. Install phpLDAPadmin using this command :

[root@centos62 ~]# yum install phpldapadmin -y
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
 * base: centos.ipserverone.com
 * epel: ftp.cuhk.edu.hk
 * extras: centos.ipserverone.com
 * updates: centos.maulvi.net
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package phpldapadmin.noarch 0:1.2.2-1.el6 will be installed
--> Processing Dependency: php-ldap for package: phpldapadmin-1.2.2-1.el6.noarch
--> Running transaction check
---> Package php-ldap.i686 0:5.3.3-3.el6_2.6 will be installed
--> Finished Dependency Resolution

Dependencies Resolved

====================================================================================================
 Package                  Arch               Version                      Repository           Size
====================================================================================================
Installing:
 phpldapadmin             noarch             1.2.2-1.el6                  epel                776 k
Installing for dependencies:
 php-ldap                 i686               5.3.3-3.el6_2.6              updates              35 k

Transaction Summary
====================================================================================================
Install       2 Package(s)

Total download size: 811 k
Installed size: 2.3 M
Downloading Packages:
(1/2): php-ldap-5.3.3-3.el6_2.6.i686.rpm                                     |  35 kB     00:00
(2/2): phpldapadmin-1.2.2-1.el6.noarch.rpm                                   | 776 kB     00:08
----------------------------------------------------------------------------------------------------
Total                                                                62 kB/s | 811 kB     00:13
Running rpm_check_debug
Running Transaction Test
Transaction Test Succeeded
Running Transaction
  Installing : php-ldap-5.3.3-3.el6_2.6.i686                                                    1/2
  Installing : phpldapadmin-1.2.2-1.el6.noarch                                                  2/2

Installed:
  phpldapadmin.noarch 0:1.2.2-1.el6

Dependency Installed:
  php-ldap.i686 0:5.3.3-3.el6_2.6

Complete!

2. Configure phpLDAPadmin. Allow 198.168.1.x network to access thru phpLDAPadmin :

#
#  Web-based tool for managing LDAP servers
#

Alias /phpldapadmin /usr/share/phpldapadmin/htdocs
Alias /ldapadmin /usr/share/phpldapadmin/htdocs

<Directory /usr/share/phpldapadmin/htdocs>
  Order Deny,Allow
  Deny from all
  Allow from 127.0.0.1 192.168.1.0/24
  Allow from ::1
</Directory>

3. Restart httpd server :

[root@ldap 389 ~]# /etc/init.d/httpd restart
Stopping httpd:                                            [  OK  ]
Starting httpd:                                            [  OK  ]

4. Installation and configuration completed. Navigate and administer ldap as below URL :

http://ldap_server_ip/ldapadmin

phpLDAPadmin