Install 389 Directory Server CentOS

Install 389 Directory Server CentOS

Install 389 Directory Server CentOS

389 Directory Server logo

389 Directory server is a wonderful drop-in replacement for OpenLDAP, and is extremely easy to install and configure. A few really important features of 389 directory server is multi-master replication, a unified admin console, password policies, and the capability of sync with Active Directory. This makes 389 directory server a premium choice for Linux Administrators.

Login, and su to root

Root shell prompt on host test389 after su to root

now enable the EPEL Repo

wget of epel-release-6-8.noarch.rpm from mirrors.kernel.org/fedora-epel/6/i386
rpm -Uvh epel-release-6-8.noarch.rpm to enable the EPEL repository

now install the REMI Repo

wget of remi-release-6.rpm from rpms.famillecollet.com/enterprise
rpm -Uvh remi-release-6.rpm to install the Remi repository

edit /etc/hosts to include your hostname/ipaddress

now edit the syscontrol configuration

vi /etc/sysctl.conf opened as root on test389

add lines 44-47

sysctl.conf lines 44-47: net.ipv4.tcp_keepalive_time 300, ip_local_port_range 1024 65000, fs.file-max 64000

now edit the security limits configuration

vi /etc/security/limits.conf opened as root

add lines 50 and 51 to the end of the configuration file

limits.conf lines 50-51: soft and hard nofile 8192 for all users

now edit /etc/profile

vi /etc/profile opened as root

add line 79

/etc/profile line 79: ulimit -n 8192

create a local service account to run 389 as

useradd ldapadmin creating the 389 service account

set password

passwd ldapadmin: all authentication tokens updated successfully

now install the 389 directory server packages

yum install -y 389-ds openldap-clients

run the installer for 389

setup-ds-admin.pl typed at the root prompt to start the 389 setup

choose setup type 2

setup-ds-admin.pl setup type menu: Express, Typical, Custom, with 2 (Typical) chosen

for the next step type “servername.domain.local” or whatever your scheme is,w e are going with 389.domain.local

set the system user as ldapadmin

System User and System Group both set to ldapadmin

fill out as follows

Setup prompts: configuration directory admin ID, Administration Domain domain.local, port 389

hit yes to setup the server

Setup prompts: suffix dc=domain,dc=local, Directory Manager DN, admin port 9830, ready to set up: yes

now make sure the necessary services start on startup

chkconfig dirsrv on and chkconfig dirsrv-admin on

now in order to launch the admin console, we need to have X installed (or you can install on a remote server, but for now let’s install on the master LDAP server)

yum -y groupinstall Desktop, Desktop Platform, X Window System and Fonts

one all 400 or so packages are done installing, reboot

once rebooted, verify that you can launch the 389 console via ssh X Session

ssh -X root@test389.domain.local /usr/bin/389-console -a http://test389.domain.local:9830

you should be prompted with a login screen

389 Management Console Login dialog with User ID, Password and Administration URL

enter your credentials as follows:

389 console login filled in: user admin, Administration URL http://test389.domain.local:9830

here’s the console window

389 Management Console Users and Groups tab for domain.local, directory test389.domain.local:389

from here you are ready to start adding users/groups to LDAP under “Directory Server” –> Directory –> domain

Here’s a few more steps you may want to know about:

  • To Configure MultiMaster Replication click here
  • To Join Client to 389 Directory Server click here
  • To Sync Active Directory With 389 Directory Server click here
  • To Configure TLS/SSL Secure LDAP click here
  • To Configure TLS/SSL Client click here
  • To Configure a Password Policy/Lockout, click here
  • To add the Samba Schema to 389 LDAP click here
  • To add the SUDO Schema to 389 LDAP click here
  • To add your Automount/Autofs configuration to LDAP click here
  • To configure LDAP host access using 389 click here
  • To disable Anonymous LDAP Bind, click here
  • To Authenticate Windows 7 Against LDAP click here
  • To Authenticate Windows 7 using TLS/SSL click here
  • To Configure a Samba server to use pGina click here
  • To configure your LDAP server as an internal DNS server click here
  • To configure yoru LDAP server to use Dynamic DNS click here
  • To configure your LDAP server as a DHCP server click here
  • To configure your LDAP server as a NTP server click here

That’s it!

Hosted Linux Servers at www.zwiegnet.com/go

Leave a Reply

Your email address will not be published. Required fields are marked *