4. Install the 389 Directory Server packages :<\/p>\n
[root@ldap ~]# yum install 389-ds -y\n<\/pre>\n5. Fix Error: command ‘getsebool httpd_can_connect_ldap’ failed – output [getsebool: SELinux is disabled :<\/p>\n
[root@ldap ~]# mkdir ~\/bin\n[root@ldap ~]# vi ~\/bin\/getsebool\n<\/pre>\n#!\/bin\/sh\necho on\nexit 0\n<\/pre>\n[root@ldap ~]# vi ~\/bin\/setsebool\n<\/pre>\n#!\/bin\/sh\nexit 0\n<\/pre>\n[root@ldap ~]# chmod +x ~\/bin\/*sebool\n<\/pre>\n6. Run setup script to start configure the ldap service :<\/p>\n
[root@ldap ~]# PATH=~\/bin:$PATH setup-ds-admin.pl\n\n==============================================================================\nThis program will set up the 389 Directory and Administration Servers.\n\nIt is recommended that you have \"root\" privilege to set up the software.\nTips for using this program:\n - Press \"Enter\" to choose the default and go to the next screen\n - Type \"Control-B\" then \"Enter\" to go back to the previous screen\n - Type \"Control-C\" to cancel the setup program\n\nWould you like to continue with set up? [yes]:\n\n==============================================================================\nYour system has been scanned for potential problems, missing patches,\netc. The following output is a report of the items found that need to\nbe addressed before running this software in a production\nenvironment.\n\n389 Directory Server system tuning analysis version 23-FEBRUARY-2012.\n\nNOTICE : System is x86_64-unknown-linux2.6.32-431.el6.x86_64 (1 processor).\n\nWould you like to continue? [yes]:\n\n==============================================================================\nChoose a setup type:\n\n 1. Express\n Allows you to quickly set up the servers using the most\n common options and pre-defined defaults. Useful for quick\n evaluation of the products.\n\n 2. Typical\n Allows you to specify common defaults and options.\n\n 3. Custom\n Allows you to specify more advanced options. This is\n recommended for experienced server administrators only.\n\nTo accept the default shown in brackets, press the Enter key.\n\nChoose a setup type [2]:\n\n==============================================================================\nEnter the fully qualified domain name of the computer\non which you're setting up server software. Using the form\n.\nExample: eros.example.com.\n\nTo accept the default shown in brackets, press the Enter key.\n\nWarning: This step may take a few minutes if your DNS servers\ncan not be reached or if DNS is not configured correctly. If\nyou would rather not wait, hit Ctrl-C and run this program again\nwith the following command line option to specify the hostname:\n\n General.FullMachineName=your.hostname.domain.name\n\nComputer name [ldap.ehowstuff.local]:\n\nWARNING: There are problems with the hostname.\nHostname 'ldap.ehowstuff.local' is valid, but none of the IP addresses\nresolve back to ldap.ehowstuff.local\n- address 192.168.0.5 resolves to host centos6.5.ehowstuff.local\n\nPlease check the spelling of the hostname and\/or your network configuration.\nIf you proceed with this hostname, you may encounter problems.\n\nDo you want to proceed with hostname 'ldap.ehowstuff.local'? [no]: yes\n\n==============================================================================\nThe servers must run as a specific user in a specific group.\nIt is strongly recommended that this user should have no privileges\non the computer (i.e. a non-root user). The setup procedure\nwill give this user\/group some permissions in specific paths\/files\nto perform server-specific operations.\n\nIf you have not yet created a user and group for the servers,\ncreate this user and group using your native operating\nsystem utilities.\n\nSystem User [nobody]:\nSystem Group [nobody]:\n\n==============================================================================\nServer information is stored in the configuration directory server.\nThis information is used by the console and administration server to\nconfigure and manage your servers. If you have already set up a\nconfiguration directory server, you should register any servers you\nset up or create with the configuration server. To do so, the\nfollowing information about the configuration server is required: the\nfully qualified host name of the form\n.(e.g. hostname.example.com), the port number\n(default 389), the suffix, the DN and password of a user having\npermission to write the configuration information, usually the\nconfiguration directory administrator, and if you are using security\n(TLS\/SSL). If you are using TLS\/SSL, specify the TLS\/SSL (LDAPS) port\nnumber (default 636) instead of the regular LDAP port number, and\nprovide the CA certificate (in PEM\/ASCII format).\n\nIf you do not yet have a configuration directory server, enter 'No' to\nbe prompted to set up one.\n\nDo you want to register this software with an existing\nconfiguration directory server? [no]:\n\n==============================================================================\nPlease enter the administrator ID for the configuration directory\nserver. This is the ID typically used to log in to the console. You\nwill also be prompted for the password.\n\nConfiguration directory server\nadministrator ID [admin]:\nPassword:\nPassword (confirm):\n\n==============================================================================\nThe information stored in the configuration directory server can be\nseparated into different Administration Domains. If you are managing\nmultiple software releases at the same time, or managing information\nabout multiple domains, you may use the Administration Domain to keep\nthem separate.\n\nIf you are not using administrative domains, press Enter to select the\ndefault. Otherwise, enter some descriptive, unique name for the\nadministration domain, such as the name of the organization\nresponsible for managing the domain.\n\nAdministration Domain [ehowstuff.local]:\n\n==============================================================================\nThe standard directory server network port number is 389. However, if\nyou are not logged as the superuser, or port 389 is in use, the\ndefault value will be a random unused port number greater than 1024.\nIf you want to use port 389, make sure that you are logged in as the\nsuperuser, that port 389 is not in use.\n\nDirectory server network port [389]:\n\n==============================================================================\nEach instance of a directory server requires a unique identifier.\nThis identifier is used to name the various\ninstance specific files and directories in the file system,\nas well as for other uses as a server instance identifier.\n\nDirectory server identifier [ldap]:\n\n==============================================================================\nThe suffix is the root of your directory tree. The suffix must be a valid DN.\nIt is recommended that you use the dc=domaincomponent suffix convention.\nFor example, if your domain is example.com,\nyou should use dc=example,dc=com for your suffix.\nSetup will create this initial suffix for you,\nbut you may have more than one suffix.\nUse the directory server utilities to create additional suffixes.\n\nSuffix [dc=ehowstuff, dc=local]:\n\n==============================================================================\nCertain directory server operations require an administrative user.\nThis user is referred to as the Directory Manager and typically has a\nbind Distinguished Name (DN) of cn=Directory Manager.\nYou will also be prompted for the password for this user. The password must\nbe at least 8 characters long, and contain no spaces.\nPress Control-B or type the word \"back\", then Enter to back up and start over.\n\nDirectory Manager DN [cn=Directory Manager]:\nPassword:\nPassword (confirm):\n\n==============================================================================\nThe Administration Server is separate from any of your web or application\nservers since it listens to a different port and access to it is\nrestricted.\n\nPick a port number between 1024 and 65535 to run your Administration\nServer on. You should NOT use a port number which you plan to\nrun a web or application server on, rather, select a number which you\nwill remember and which will not be used for anything else.\n\nAdministration port [9830]:\n\n==============================================================================\nThe interactive phase is complete. The script will now set up your\nservers. Enter No or go Back if you want to change something.\n\nAre you ready to set up your servers? [yes]:\nCreating directory server . . .\nWarning: Hostname ldap.ehowstuff.local is valid, but none of the IP addresses\nresolve back to ldap.ehowstuff.local\n address 192.168.0.5 resolves to host centos6.5.ehowstuff.local\nYour new DS instance 'ldap' was successfully created.\nCreating the configuration directory server . . .\nBeginning Admin Server reconfiguration . . .\nCreating Admin Server files and directories . . .\nUpdating adm.conf . . .\nUpdating admpw . . .\nRegistering admin server with the configuration directory server . . .\nUpdating adm.conf with information from configuration directory server . . .\nUpdating the configuration for the httpd engine . . .\nStarting admin server . . .\noutput: Starting dirsrv-admin:\noutput: [ OK ]\nThe admin server was successfully started.\nAdmin server was successfully reconfigured and started.\nExiting . . .\nLog file is '\/tmp\/setupGwS8hs.log'\n<\/pre>\n7. Start dirsrv and dirsrv-admin service :<\/p>\n
[root@ldap ~]# \/etc\/init.d\/dirsrv start\n[root@ldap ~]# \/etc\/init.d\/dirsrv-admin start\n<\/pre>\n8. Make dirsrv and dirsrv-admin service auto start at boot :<\/p>\n
[root@ldap ~]# chkconfig dirsrv on\n[root@ldap ~]# chkconfig dirsrv-admin on\n<\/pre>\n9. Configure Iptables to allow server listen on port 22, 389 and 9830 :<\/p>\n
# Firewall configuration written by system-config-firewall\n# Manual customization of this file is not recommended.\n*filter\n:INPUT ACCEPT [0:0]\n:FORWARD ACCEPT [0:0]\n:OUTPUT ACCEPT [0:0]\n-A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT\n-A INPUT -p icmp -j ACCEPT\n-A INPUT -i lo -j ACCEPT\n-A INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT\n-A INPUT -m state --state NEW -m tcp -p tcp --dport 389 -j ACCEPT\n-A INPUT -m state --state NEW -m tcp -p tcp --dport 9830 -j ACCEPT\n-A INPUT -j REJECT --reject-with icmp-host-prohibited\n-A FORWARD -j REJECT --reject-with icmp-host-prohibited\nCOMMIT\n<\/pre>\nRestart iptables to take effect the changes :<\/p>\n
[root@ldap ~]# service iptables restart\niptables: Applying firewall rules: [ OK ]\n<\/pre>\n10. Verify port listen by the server using netstat :<\/p>\n
[root@ldap ~]# netstat -plunt | grep LISTEN\ntcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 1083\/rpcbind\ntcp 0 0 0.0.0.0:10000 0.0.0.0:* LISTEN 1125\/perl\ntcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 1116\/sshd\ntcp 0 0 0.0.0.0:9830 0.0.0.0:* LISTEN 1508\/httpd.worker\ntcp 0 0 127.0.0.1:9000 0.0.0.0:* LISTEN 1126\/php-fpm\ntcp 0 0 :::8140 :::* LISTEN 1161\/httpd\ntcp 0 0 :::111 :::* LISTEN 1083\/rpcbind\ntcp 0 0 :::80 :::* LISTEN 1161\/httpd\ntcp 0 0 :::22 :::* LISTEN 1116\/sshd\ntcp 0 0 :::443 :::* LISTEN 1161\/httpd\ntcp 0 0 :::8443 :::* LISTEN 1161\/httpd\ntcp 0 0 :::389 :::* LISTEN 1391\/.\/ns-slapd\n<\/pre>\n11. Verify port listen by the server and opened by iptables firewall :<\/p>\n
[root@ldap ~]# iptables -nL\nChain INPUT (policy ACCEPT)\ntarget prot opt source destination\nACCEPT all -- 0.0.0.0\/0 0.0.0.0\/0 state RELATED,ESTABLISHED\nACCEPT icmp -- 0.0.0.0\/0 0.0.0.0\/0\nACCEPT all -- 0.0.0.0\/0 0.0.0.0\/0\nACCEPT tcp -- 0.0.0.0\/0 0.0.0.0\/0 state NEW tcp dpt:22\nACCEPT tcp -- 0.0.0.0\/0 0.0.0.0\/0 state NEW tcp dpt:389\nACCEPT tcp -- 0.0.0.0\/0 0.0.0.0\/0 state NEW tcp dpt:9830\nREJECT all -- 0.0.0.0\/0 0.0.0.0\/0 reject-with icmp-host-prohibited\n\nChain FORWARD (policy ACCEPT)\ntarget prot opt source destination\nREJECT all -- 0.0.0.0\/0 0.0.0.0\/0 reject-with icmp-host-prohibited\n\nChain OUTPUT (policy ACCEPT)\ntarget prot opt source destination\n<\/pre>\n","protected":false},"excerpt":{"rendered":"A 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\u00a0389 LDAP Directory Server…<\/p>\n","protected":false},"author":6,"featured_media":6348,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"wds_primary_category":0,"footnotes":""},"categories":[1102,2062],"tags":[1178,1244,1536,1546],"class_list":["post-5253","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-389-directory-server","category-yum","tag-389-directory","tag-centos","tag-linux","tag-linux-utilities"],"_links":{"self":[{"href":"https:\/\/webhostinggeeks.com\/howto\/wp-json\/wp\/v2\/posts\/5253","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/webhostinggeeks.com\/howto\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/webhostinggeeks.com\/howto\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/webhostinggeeks.com\/howto\/wp-json\/wp\/v2\/users\/6"}],"replies":[{"embeddable":true,"href":"https:\/\/webhostinggeeks.com\/howto\/wp-json\/wp\/v2\/comments?post=5253"}],"version-history":[{"count":0,"href":"https:\/\/webhostinggeeks.com\/howto\/wp-json\/wp\/v2\/posts\/5253\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/webhostinggeeks.com\/howto\/wp-json\/wp\/v2\/media\/6348"}],"wp:attachment":[{"href":"https:\/\/webhostinggeeks.com\/howto\/wp-json\/wp\/v2\/media?parent=5253"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/webhostinggeeks.com\/howto\/wp-json\/wp\/v2\/categories?post=5253"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/webhostinggeeks.com\/howto\/wp-json\/wp\/v2\/tags?post=5253"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
![\"Install](\"https:\/\/webhostinggeeks.com\/howto\/wp-content\/uploads\/2014\/07\/centos-389.png\")
A 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\u00a0389 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\u2019s community-supported Fedora Project.<\/p>\n