Identity Management with IPA

Introduction:

FreeIPA is a Red Hat sponsored open source project which aims to provide an easily managed Identity, Policy and Audit (IPA) suite primarily targeted towards networks of Linux and Unix computers.

Assumption:

1. Domain: example.com
2. Netbios name: EXAMPLE
3. Hostname: ipa-srv1.example.com

Note:

Before start the installation make sure system has static IP configured, all softwares are up to date and have made the changes hostname entry in host file.

Network Configuration:

[root@ipa-srv1 ~]# vi /etc/sysconfig/network-scripts/ifcfg-eth0
DEVICE=”eth0″
HWADDR=”00:0C:29:CE:91:33″
NM_CONTROLLED=”no”
ONBOOT=”yes”
IPADDR=10.x.x.41
PREFIX=24
GATEWAY=10.x.x.1

System Update:

[root@ipa-srv1 ~]#yum update -y //to update the system

Host Entry:

[root@ipa-srv1 ~]# vi /etc/hosts //host file path

10.x.x.x ipa-srv1.example.com ipa-srv1 //host file entry

[root@ipa-srv1 ~]#reboot

Software Dependecies:

yum install bind bind-dyndb-ldap -y

Installation & Configuration:

[root@ipa-srv1 ~]#yum install ipa-server -y

[root@ipa-srv1 ~]# ipa-server-install –setup-dns

The log file for this installation can be found in /var/log/ipaserver-install.log
==============================================================================
This program will set up the IPA Server.

This includes:
* Configure a stand-alone CA (dogtag) for certificate management
* Configure the Network Time Daemon (ntpd)
* Create and configure an instance of Directory Server
* Create and configure a Kerberos Key Distribution Center (KDC)
* Configure Apache (httpd)
* Configure DNS (bind)

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

Existing BIND configuration detected, overwrite? [no]: yes
Enter the fully qualified domain name of the computer
on which you’re setting up server software. Using the form
.
Example: master.example.com.

Server host name [ipa-srv1.example.com]:

Warning: skipping DNS resolution of host ipa-srv1.example.com
The domain name has been determined based on the host name.

Please confirm the domain name [example.com]:

Unable to resolve IP address for host name
Please provide the IP address to be used for this host name: 10.x.x.x
Adding [10.x.x.x ipa-srv1.example.com] to your /etc/hosts file
The kerberos protocol requires a Realm name to be defined.
This is typically the domain name converted to uppercase.

Please provide a realm name [EXAMPLE.COM]:
Certain directory server operations require an administrative user.
This user is referred to as the Directory Manager and has full access
to the Directory for system management tasks and will be added to the
instance of directory server created for IPA.
The password must be at least 8 characters long.

Directory Manager password:
Password (confirm):

The IPA server requires an administrative user, named ‘admin’.
This user is a regular system account used for IPA server administration.

IPA admin password:
Password (confirm):

Do you want to configure DNS forwarders? [yes]:
Enter the IP address of DNS forwarder to use, or press Enter to finish.
Enter IP address for a DNS forwarder: 10.x.x.x
DNS forwarder 10.x.x.x added
Enter IP address for a DNS forwarder:
Do you want to configure the reverse zone? [yes]:
Please specify the reverse zone name [x.x.10.in-addr.arpa.]:
Using reverse zone x.x.10.in-addr.arpa.

The IPA Master Server will be configured with:
Hostname: ipa-srv1.example.com
IP address: 10.x.x.x
Domain name: example.com
Realm name: example.COM

BIND DNS server will be configured to serve IPA domain with:
Forwarders: 10.x.x.x
Reverse zone: x.x.10.in-addr.arpa.

Continue to configure the system with these values? [no]: yes

The following operations may take some minutes to complete.
Please wait until the prompt is returned.

Configuring NTP daemon (ntpd)
[1/4]: stopping ntpd
[2/4]: writing configuration
[3/4]: configuring ntpd to start on boot
[4/4]: starting ntpd
Done configuring NTP daemon (ntpd).
Configuring directory server for the CA (pkids): Estimated time 30 minutes 30 seconds
[1/3]: creating directory server user
[2/3]: creating directory server instance
[3/3]: restarting directory server
Done configuring directory server for the CA (pkids).
Configuring certificate server (pki-cad): Estimated time 33 minutes 30 seconds
[1/21]: creating certificate server user
[2/21]: creating pki-ca instance
[3/21]: configuring certificate server instance
[4/21]: disabling nonces
[5/21]: creating CA agent PKCS#12 file in /root
[6/21]: creating RA agent certificate database
[7/21]: importing CA chain to RA certificate database
[8/21]: fixing RA database permissions
[9/21]: setting up signing cert profile
[10/21]: set up CRL publishing
[11/21]: set certificate subject base
[12/21]: enabling Subject Key Identifier
[13/21]: setting audit signing renewal to 2 years
[14/21]: configuring certificate server to start on boot
[15/21]: restarting certificate server
[16/21]: requesting RA certificate from CA
[17/21]: issuing RA agent certificate
[18/21]: adding RA agent as a trusted user
[19/21]: configure certificate renewals
[20/21]: configure Server-Cert certificate renewal
[21/21]: Configure HTTP to proxy connections
Done configuring certificate server (pki-cad).
Configuring directory server (dirsrv): Estimated time 31 minutes
[1/38]: creating directory server user
[2/38]: creating directory server instance
[3/38]: adding default schema
[4/38]: enabling memberof plugin
[5/38]: enabling winsync plugin
[6/38]: configuring replication version plugin
[7/38]: enabling IPA enrollment plugin
[8/38]: enabling ldapi
[9/38]: disabling betxn plugins
[10/38]: configuring uniqueness plugin
[11/38]: configuring uuid plugin
[12/38]: configuring modrdn plugin
[13/38]: enabling entryUSN plugin
[14/38]: configuring lockout plugin
[15/38]: creating indices
[16/38]: enabling referential integrity plugin
[17/38]: configuring ssl for ds instance
[18/38]: configuring certmap.conf
[19/38]: configure autobind for root
[20/38]: configure new location for managed entries
[21/38]: restarting directory server
[22/38]: adding default layout
[23/38]: adding delegation layout
[24/38]: adding replication acis
[25/38]: creating container for managed entries
[26/38]: configuring user private groups
[27/38]: configuring netgroups from hostgroups
[28/38]: creating default Sudo bind user
[29/38]: creating default Auto Member layout
[30/38]: adding range check plugin
[31/38]: creating default HBAC rule allow_all
[32/38]: Upload CA cert to the directory
[33/38]: initializing group membership
[34/38]: adding master entry
[35/38]: configuring Posix uid/gid generation
[36/38]: enabling compatibility plugin
[37/38]: tuning directory server
[38/38]: configuring directory to start on boot
Done configuring directory server (dirsrv).
Configuring Kerberos KDC (krb5kdc): Estimated time 30 minutes 30 seconds
[1/10]: adding sasl mappings to the directory
[2/10]: adding kerberos container to the directory
[3/10]: configuring KDC
[4/10]: initialize kerberos container
[5/10]: adding default ACIs
[6/10]: creating a keytab for the directory
[7/10]: creating a keytab for the machine
[8/10]: adding the password extension to the directory
[9/10]: starting the KDC
[10/10]: configuring KDC to start on boot
Done configuring Kerberos KDC (krb5kdc).
Configuring kadmin
[1/2]: starting kadmin
[2/2]: configuring kadmin to start on boot
Done configuring kadmin.
Configuring ipa_memcached
[1/2]: starting ipa_memcached
[2/2]: configuring ipa_memcached to start on boot
Done configuring ipa_memcached.
Configuring the web interface (httpd): Estimated time 31 minutes
[1/13]: setting mod_nss port to 443
[2/13]: setting mod_nss password file
[3/13]: enabling mod_nss renegotiate
[4/13]: adding URL rewriting rules
[5/13]: configuring httpd
[6/13]: setting up ssl
[7/13]: setting up browser autoconfig
[8/13]: publish CA cert
[9/13]: creating a keytab for httpd
[10/13]: clean up any existing httpd ccache
[11/13]: configuring SELinux for httpd
[12/13]: restarting httpd
[13/13]: configuring httpd to start on boot
Done configuring the web interface (httpd).
Applying LDAP updates
Restarting the directory server
Restarting the KDC
Configuring DNS (named)
[1/9]: adding DNS container
[2/9]: setting up our zone
[3/9]: setting up reverse zone
[4/9]: setting up our own record
[5/9]: setting up kerberos principal
[6/9]: setting up named.conf
[7/9]: restarting named
[8/9]: configuring named to start on boot
[9/9]: changing resolv.conf to point to ourselves
Done configuring DNS (named).

Global DNS configuration in LDAP server is empty
You can use ‘dnsconfig-mod’ command to set global DNS options that
would override settings in local named.conf files

Restarting the web server
==============================================================================
Setup complete

Next steps:
1. You must make sure these network ports are open:
TCP Ports:
* 80, 443: HTTP/HTTPS
* 389, 636: LDAP/LDAPS
* 88, 464: kerberos
* 53: bind
UDP Ports:
* 88, 464: kerberos
* 53: bind
* 123: ntp

2. You can now obtain a kerberos ticket using the command: ‘kinit admin’
This ticket will allow you to use the IPA tools (e.g., ipa user-add)
and the web user interface.

Be sure to back up the CA certificate stored in /root/cacert.p12
This file isinit required to create replicas. The password for this
file is the Directory Manager password
[root@ipa-srv1 ~]#
10.101.10.14

#IPATABLE Setting in Centos 6

[root@ipa-srv1 ~]# iptables -N IPA
[root@ipa-srv1 ~]# iptables -I INPUT 5 -j IPA
[root@ipa-srv1 ~]# iptables -I IPA -s 0.0.0.0/0 -p udp –dport 53 -j ACCEPT
[root@ipa-srv1 ~]# iptables -I IPA -s 0.0.0.0/0 -p udp –dport 88 -j ACCEPT
[root@ipa-srv1 ~]# iptables -I IPA -s 0.0.0.0/0 -p udp –dport 123 -j ACCEPT
[root@ipa-srv1 ~]# iptables -I IPA -s 0.0.0.0/0 -p udp –dport 464 -j ACCEPT
[root@ipa-srv1 ~]# iptables -I IPA -s 0.0.0.0/0 -p tcp –dport 53 -j ACCEPT
[root@ipa-srv1 ~]# iptables -I IPA -s 0.0.0.0/0 -p tcp –dport 80 -j ACCEPT
[root@ipa-srv1 ~]# iptables -I IPA -s 0.0.0.0/0 -p tcp –dport 88 -j ACCEPT
[root@ipa-srv1 ~]# iptables -I IPA -s 0.0.0.0/0 -p tcp –dport 123 -j ACCEPT
[root@ipa-srv1 ~]# iptables -I IPA -s 0.0.0.0/0 -p tcp –dport 389 -j ACCEPT
[root@ipa-srv1 ~]# iptables -I IPA -s 0.0.0.0/0 -p tcp –dport 464 -j ACCEPT
[root@ipa-srv1 ~]# iptables -I IPA -s 0.0.0.0/0 -p tcp –dport 443 -j ACCEPT
[root@ipa-srv1 ~]# iptables -I IPA -s 0.0.0.0/0 -p tcp –dport 636 -j ACCEPT
[root@ipa-srv1 ~]# service iptables save
iptables: Saving firewall rules to /etc/sysconfig/iptables:[ OK ]
[root@ipa-srv1 ~]#

Extra:

If  you have centos 7 or Redhat 7 then you can set firewall rule as:

[root@ipa-srv1 ~]#firewall-cmd –zone=public –add-port=53/udp –permanent

[root@ipa-srv1 ~]#firewall-cmd –zone=public –add-port=88/udp –permanent

[root@ipa-srv1 ~]#firewall-cmd –zone=public –add-port=123/udp –permanent

[root@ipa-srv1 ~]#firewall-cmd –zone=public –add-port=464/udp –permanent

[root@ipa-srv1 ~]#firewall-cmd –zone=public –add-port=53/tcp –permanent

[root@ipa-srv1 ~]#firewall-cmd –zone=public –add-port=88/tcp –permanent

[root@ipa-srv1 ~]#firewall-cmd –zone=public –add-port=123/tcp –permanent

[root@ipa-srv1 ~]#firewall-cmd –zone=public –add-port=389/tcp –permanent

[root@ipa-srv1 ~]#firewall-cmd –zone=public –add-port=464/tcp –permanent

[root@ipa-srv1 ~]#firewall-cmd –zone=public –add-port=443/tcp –permanent

[root@ipa-srv1 ~]#firewall-cmd –zone=public –add-port=636/tcp –permanent

[root@ipa-srv1 ~]#firewall-cmd –reload

[root@ipa-srv1 ~]#systemctl start firewalld.service

[root@ipa-srv1 ~]#systemctl enable firewalld.service

Different remedies existing from the Web to why to waste period and visit dispensary if you can easily purchase medications sit at home. There are numerous of legal online drugstores that will deliver remedies to your home. If you are considering Cialis, you probably want to study more about Cialis. (See also Amoxicillin Over the Counter). This website provides you with some useful info on the benefits of remedies and how they are evaluated for security. Generally, both men and women are afflicted by sexual disorders. Often, when folk think about Cialis, they mean Generic Amoxil Amoxicillin. The very momentous question you must look for is Cialis. (Read more Other Forms of Metronidazole). Finally, such kind of difficulties can be an early warning symptom of serious health problems, such as heart disease. Finally ordering remedies online can save money, but keep these tips in mind.