You need at least 2 Servers:

Setup:

node1.domain1.example.com – IPA Server

node2.domain1.example.com – IPA Client

Installing IPA Server:

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

[root@node1 ~]# yum install bind-dyndb-ldap bind (make sure you install bind package if you wnated to configure IPA with DNS setup)

[root@node1 ~]# ipa-server-install –hostname=node1.domain1.example.com –domain=domain1.example.com –realm=DOMAIN1.EXAMPLE.COM -p redhat13 -a redhat13 –no-ntp  –setup-dns  –no-forwarders -U

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
* Create and configure an instance of Directory Server
* Create and configure a Kerberos Key Distribution Center (KDC)
* Configure Apache (httpd)
* Configure DNS (bind)

Excluded by options:
* Configure the Network Time Daemon (ntpd)

Warning: skipping DNS resolution of host node1.domain1.example.com
Using reverse zone 0.168.192.in-addr.arpa.

The IPA Master Server will be configured with:
Hostname:      node1.domain1.example.com
IP address:    192.168.0.150
Domain name:   domain1.example.com
Realm name:    DOMAIN1.EXAMPLE.COM

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

Configuring directory server (dirsrv): Estimated time 1 minute
[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]: configuring uniqueness plugin
[10/38]: configuring uuid plugin
[11/38]: configuring modrdn plugin
[12/38]: configuring DNS plugin
[13/38]: enabling entryUSN plugin
[14/38]: configuring lockout plugin
[15/38]: creating indices
[16/38]: enabling referential integrity plugin
[17/38]: configuring certmap.conf
[18/38]: configure autobind for root
[19/38]: configure new location for managed entries
[20/38]: configure dirsrv ccache
[21/38]: enable SASL mapping fallback
[22/38]: restarting directory server
[23/38]: adding default layout
[24/38]: adding delegation layout
[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]: initializing group membership
[33/38]: adding master entry
[34/38]: configuring Posix uid/gid generation
[35/38]: adding replication acis
[36/38]: enabling compatibility plugin
[37/38]: tuning directory server
[38/38]: configuring directory to start on boot
Done configuring directory server (dirsrv).
Configuring certificate server (pki-tomcatd): Estimated time 3 minutes 30 second
[1/22]: creating certificate server user
[2/22]: configuring certificate server instance
[3/22]: stopping certificate server instance to update CS.cfg
[4/22]: disabling nonces
[5/22]: set up CRL publishing
[6/22]: starting certificate server instance
[7/22]: creating RA agent certificate database
[8/22]: importing CA chain to RA certificate database
[9/22]: fixing RA database permissions
[10/22]: setting up signing cert profile
[11/22]: set certificate subject base
[12/22]: enabling Subject Key Identifier
[13/22]: enabling CRL and OCSP extensions for certificates
[14/22]: setting audit signing renewal to 2 years
[15/22]: configuring certificate server to start on boot
[16/22]: restarting certificate server
[17/22]: requesting RA certificate from CA
[18/22]: issuing RA agent certificate
[19/22]: adding RA agent as a trusted user
[20/22]: configure certificate renewals
[21/22]: configure Server-Cert certificate renewal
[22/22]: Configure HTTP to proxy connections
Done configuring certificate server (pki-tomcatd).
Configuring Kerberos KDC (krb5kdc): Estimated time 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 ipa-otpd
[1/2]: starting ipa-otpd
[2/2]: configuring ipa-otpd to start on boot
Done configuring ipa-otpd.
Configuring the web interface (httpd): Estimated time 1 minute
[1/14]: setting mod_nss port to 443
[2/14]: setting mod_nss password file
[3/14]: enabling mod_nss renegotiate
[4/14]: adding URL rewriting rules
[5/14]: configuring httpd
[6/14]: setting up ssl
[7/14]: setting up browser autoconfig
[8/14]: publish CA cert
[9/14]: creating a keytab for httpd
[10/14]: clean up any existing httpd ccache
[11/14]: configuring SELinux for httpd
[12/14]: configure httpd ccache
[13/14]: restarting httpd
[14/14]: configuring httpd to start on boot
Done configuring the web interface (httpd).
Applying LDAP updates
Restarting the directory server
Restarting the KDC
Restarting the certificate server
Configuring DNS (named)
[1/11]: adding DNS container
[2/11]: setting up our zone
[3/11]: setting up reverse zone
[4/11]: setting up our own record
[5/11]: setting up records for other masters
[6/11]: setting up CA record
[7/11]: setting up kerberos principal
[8/11]: setting up named.conf
[9/11]: restarting named
[10/11]: configuring named to start on boot
[11/11]: 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

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.
3. Kerberos requires time synchronization between clients
and servers for correct operation. You should consider enabling ntpd.

Be sure to back up the CA certificate stored in /root/cacert.p12
This file is required to create replicas. The password for this
file is the Directory Manager password

Creating Users:

[root@node1 ~]# systemctl restart  sshd.service
[root@node1 ~]# kinit admin
Password for admin@DOMAIN1.EXAMPLE.COM:
[root@node1 ~]# ipa user-add thussain –first=Touqeer –last=Hussain –password

Password:
Enter Password again to verify:
———————
Added user “thussain”
———————
User login: thussain
First name: Touqeer
Last name: Hussain
Full name: Touqeer Hussain
Display name: Touqeer Hussain
Initials: TH
Home directory: /home/thussain
GECOS: Touqeer Hussain
Login shell: /bin/sh
Kerberos principal: thussain@DOMAIN1.EXAMPLE.COM
Email address: thussain@domain1.example.com
UID: 285400001
GID: 285400001
Password: True
Member of groups: ipausers
Kerberos keys available: True
[root@node1 ~]# ipa user-add bzaman –first=Badi –last=Zaman –password
Password:
Enter Password again to verify:
** Passwords do not match! **
Password:
Enter Password again to verify:
——————-
Added user “bzaman”
——————-
User login: bzaman
First name: Badi
Last name: Zaman
Full name: Badi Zaman
Display name: Badi Zaman
Initials: BZ
Home directory: /home/bzaman
GECOS: Badi Zaman
Login shell: /bin/sh
Kerberos principal: bzaman@DOMAIN1.EXAMPLE.COM
Email address: bzaman@domain1.example.com
UID: 285400003
GID: 285400003
Password: True
Member of groups: ipausers
Kerberos keys available: True

Creting Group:

ipa group-add Lions –desc=Lions Group

Adding Users into Lions Group:

user add into group

 

IPA Clinet Installation and Configuration:

This installation we will start on node2

[root@node2 ~]# yum install -y ipa-client.x86_64  ipa-admintools.x86_64
[root@node2 ~]# ipa-client-install –domain=domain1.example.com –server=node1.domain1.example.com –realm=DOMAIN1.EXAMPLE.COM -p admin -w redhat13 –mkhomedir -U
Hostname: node2.domain1.example.com
Realm: DOMAIN1.EXAMPLE.COM
DNS Domain: domain1.example.com
IPA Server: node1.domain1.example.com
BaseDN: dc=domain1,dc=example,dc=com

Synchronizing time with KDC…
Unable to sync time with IPA NTP server, assuming the time is in sync. Please check that 123 UDP port is opened.
Successfully retrieved CA cert
Subject:     CN=Certificate Authority,O=DOMAIN1.EXAMPLE.COM
Issuer:      CN=Certificate Authority,O=DOMAIN1.EXAMPLE.COM
Valid From:  Thu Jul 24 16:04:11 2014 UTC
Valid Until: Mon Jul 24 16:04:11 2034 UTC

Enrolled in IPA realm DOMAIN1.EXAMPLE.COM
Created /etc/ipa/default.conf
New SSSD config will be created
Configured /etc/sssd/sssd.conf
Configured /etc/krb5.conf for IPA realm DOMAIN1.EXAMPLE.COM
trying https://node1.domain1.example.com/ipa/xml
Forwarding ‘ping’ to server ‘https://node1.domain1.example.com/ipa/xml’
Forwarding ‘env’ to server ‘https://node1.domain1.example.com/ipa/xml’
Hostname (node2.domain1.example.com) not found in DNS
Failed to update DNS records.
Adding SSH public key from /etc/ssh/ssh_host_rsa_key.pub
Adding SSH public key from /etc/ssh/ssh_host_ecdsa_key.pub
Forwarding ‘host_mod’ to server ‘https://node1.domain1.example.com/ipa/xml’
Could not update DNS SSHFP records.
SSSD enabled
Configured /etc/openldap/ldap.conf
NTP enabled
Configured /etc/ssh/ssh_config
Configured /etc/ssh/sshd_config
Client configuration complete.

[root@node2 ~]# kinit admin
Password for admin@DOMAIN1.EXAMPLE.COM:
[root@node2 ~]#
[root@node2 ~]#
[root@node2 ~]# su – admin
Creating home directory for admin.
[admin@node2 ~]$
[admin@node2 ~]$
[admin@node2 ~]$
[admin@node2 ~]$ exit
logout
[root@node2 ~]# su – thussain
[thussain@node2 ~]$
[thussain@node2 ~]$
[thussain@node2 ~]$ logout
[root@node2 ~]# su – bzaman
Creating home directory for bzaman.
-sh-4.2$

 

Upcoming post:

1. RBAC – Role Based Access Control

2. HBAC – Host Based Access Control

3. Sudo access

4. automount home dir

 

 

 

Recommended For You.

With a heavy heart Debian  mourns the passing of Ian Murdock, stalwart proponent of Free Open Source Software, Father, Son,