Bits, Bytes, & Radio Waves

A quiet journey through discovery and understanding.

Exploring Red Hat Identity Management: Building a Lightweight, Open Source Lab Without Microsoft Servers

Aaron Rombaut

<Working Copy | Not everything may be complete or in correct order>

Before diving in, I want to make it clear that this post isn’t meant to replace or replicate any official Red Hat documentation. I am also not running these servers in a production environment. This post simply is a way for me to keep this configuration for future reference.

My goal here is simply to learn something new and explore alternatives to using Microsoft Windows Server for core infrastructure services like DNS, Certificate Authority (CA), NTP, and directory management through LDAP. I chose to experiment with Red Hat Enterprise Linux because it offers a smaller virtual machine footprint compared to Windows Server, making it ideal for my lab environment. Since I’m using a Red Hat Developer license for testing, I’ll likely transition to Fedora later to maintain a fully open source setup—free from both Red Hat and Microsoft licensing requirements, while still running a powerful, standards-based identity and policy management solution.

  • IPA – Version 4.12.2
  • Red Hat Enterprise Linux release 9.6 (Plow)

The official Red Hat documentation for installing Identity Management can be found, here: https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/9/html/installing_identity_management/index

Install Two Red Hat Virtual Machines

I installed two Red Hat virtual machines, choosing only basic hardware.

  • 2 vCPU
  • 4 GB RAM
  • 40 GB hard disk (thin provisioned)
  • VMware Paravirtual SCSI controller
  • VMXNET3 Network Adapter

When it comes to Software Selection, choose a basic Server.

Since these virtual machines are hosted on a hypervisor, install the Guest Agents. Red Hat documentation suggests that no other services be installed.

Configure IdM Servers

I wanted to log into SSH with the root account, so I configured the /etc/ssh/sshd_config file to include the following:

PermitRootLogin yes

Restart the sshd.service service.

systemctl restart sshd.service

At the end of this post, we will remove this so that SSH is secured again.

DNS Host Name Requirements

The /etc/hosts file must contain the following configuration:

  • The first two entries are the IPv4 and IPv6 localhost entries.
  • The next entry specifies the IdM server IPv4 address and host name.
  • The FQDN of the IdM server comes before the short name of the IdM server.
  • The IdM server host name is not part of the localhost entry.

Here is a sample of a correctly configured file.

127.0.0.1 localhost localhost.localdomain \
localhost4 localhost4.localdomain4
::1 localhost localhost.localdomain \
localhost6 localhost6.localdomain6
192.0.2.1 server.idm.example.com server
2001:DB8::1111 server.idm.example.com server

Firewall Ports for IdM

The following ports must be allowed through the Firewall.

firewall-cmd --permanent --add-port={80/tcp,443/tcp,389/tcp,636/tcp,88/tcp,88/udp,464/tcp,464/udp,53/tcp,53/udp,123/udp}

Reload the firewall-cmd configuration so the changes take place immediately.

firewall-cmd --reload

Verify the firewall is configured with firewall-cmd --list-all.

firewall-cmd --list-all
public (active)
  target: default
  icmp-block-inversion: no
  interfaces: ens192
  sources: 
  services: cockpit dhcpv6-client ssh
  ports: 80/tcp 443/tcp 389/tcp 636/tcp 88/tcp 88/udp 464/tcp 464/udp 53/tcp 53/udp 123/udp
  protocols: 
  forward: yes
  masquerade: no
  forward-ports: 
  source-ports: 
  icmp-blocks: 
  rich rules:

Download and Install the Required Packages

I want to use integrated DNS, so I require the additional package listed.

dnf install ipa-server ipa-server-dns

Snapshot

Now is a good time to take an offline snapshot.

Interactive Installation of IdM Server with Integrated DNS and CA as the root CA

Start the process with ipa-server-install.

[root@rhel-170-10 ~]# ipa-server-install

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

This includes:
  * Configure a stand-alone CA (dogtag) for certificate management
  * Configure the NTP client (chronyd)
  * Create and configure an instance of Directory Server
  * Create and configure a Kerberos Key Distribution Center (KDC)
  * Configure Apache (httpd)
  * Configure SID generation
  * Configure the KDC to enable PKINIT

To accept the default shown in brackets, press the Enter key.
Do you want to configure integrated DNS (BIND)? [no]: yes
Enter the fully qualified domain name of the computer
on which you're setting up server software. Using the form
<hostname>.<domainname>
Example: master.example.com


Server host name [rhel-170-10.lab.aaronrombaut.com]: 
Warning: skipping DNS resolution of host rhel-170-10.lab.aaronrombaut.com
The domain name has been determined based on the host name.

Please confirm the domain name [lab.aaronrombaut.com]: 
The kerberos protocol requires a Realm name to be defined.
This is typically the domain name converted to uppercase.

Please provide a realm name [LAB.AARONROMBAUT.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): 
Checking DNS domain lab.aaronrombaut.com., please wait ...
Do you want to configure DNS forwarders? [yes]: 
Following DNS servers are configured in /etc/resolv.conf: 1.1.1.1, 1.0.0.1
Do you want to configure these servers as DNS forwarders? [yes]: 
All detected DNS servers were added. You can enter additional addresses now:
Enter an IP address for a DNS forwarder, or press Enter to skip: 
DNS forwarders: 1.1.1.1, 1.0.0.1
Checking DNS forwarders, please wait ...
Do you want to search for missing reverse zones? [yes]: 
Checking DNS domain 0.17.172.in-addr.arpa., please wait ...
Do you want to create reverse zone for IP 172.17.0.10 [yes]: 
Please specify the reverse zone name [0.17.172.in-addr.arpa.]: 
Checking DNS domain 0.17.172.in-addr.arpa., please wait ...
Using reverse zone(s) 0.17.172.in-addr.arpa.
Trust is configured but no NetBIOS domain name found, setting it now.
Enter the NetBIOS name for the IPA domain.
Only up to 15 uppercase ASCII letters, digits and dashes are allowed.
Example: EXAMPLE.

NetBIOS domain name [LAB]: 
Do you want to configure chrony with NTP server or pool address? [no]: yes
Enter NTP source server addresses separated by comma, or press Enter to skip: 
Enter a NTP source pool address, or press Enter to skip: time.cloudflare.com

Here we can see a summary of all the configurations. If a mistake was made, choose no and go through the setup again. Nothing will be configured (i.e. nothing is messed up at this point) until the value is yes to configure at this step.

The IPA Master Server will be configured with:
Hostname:       rhel-170-10.lab.aaronrombaut.com
IP address(es): 172.17.0.10
Domain name:    lab.aaronrombaut.com
Realm name:     LAB.AARONROMBAUT.COM

The CA will be configured with:
Subject DN:   CN=Certificate Authority,O=LAB.AARONROMBAUT.COM
Subject base: O=LAB.AARONROMBAUT.COM
Chaining:     self-signed

BIND DNS server will be configured to serve IPA domain with:
Forwarders:       1.1.1.1, 1.0.0.1
Forward policy:   only
Reverse zone(s):  0.17.172.in-addr.arpa.

NTP pool:	time.cloudflare.com
Continue to configure the system with these values? [no]: yes

Output of IdM Installation

Skip this section if you don’t need it. This is just a capture of what took place.

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

Disabled p11-kit-proxy
Synchronizing time
Configuration of chrony was changed by installer.
Attempting to sync time with chronyc.
Time synchronization was successful.
Configuring directory server (dirsrv). Estimated time: 30 seconds
  [1/43]: creating directory server instance
Validate installation settings ...
Create file system structures ...
Perform SELinux labeling ...
Create database backend: dc=lab,dc=aaronrombaut,dc=com ...
Perform post-installation tasks ...
  [2/43]: tune ldbm plugin
  [3/43]: adding default schema
  [4/43]: enabling memberof plugin
  [5/43]: enabling winsync plugin
  [6/43]: configure password logging
  [7/43]: configuring replication version plugin
  [8/43]: enabling IPA enrollment plugin
  [9/43]: configuring uniqueness plugin
  [10/43]: configuring uuid plugin
  [11/43]: configuring modrdn plugin
  [12/43]: configuring DNS plugin
  [13/43]: enabling entryUSN plugin
  [14/43]: configuring lockout plugin
  [15/43]: configuring graceperiod plugin
  [16/43]: configuring topology plugin
  [17/43]: creating indices
  [18/43]: enabling referential integrity plugin
  [19/43]: configuring certmap.conf
  [20/43]: configure new location for managed entries
  [21/43]: configure dirsrv ccache and keytab
  [22/43]: enabling SASL mapping fallback
  [23/43]: restarting directory server
  [24/43]: adding sasl mappings to the directory
  [25/43]: adding default layout
  [26/43]: adding delegation layout
  [27/43]: creating container for managed entries
  [28/43]: configuring user private groups
  [29/43]: configuring netgroups from hostgroups
  [30/43]: creating default Sudo bind user
  [31/43]: creating default Auto Member layout
  [32/43]: adding range check plugin
  [33/43]: creating default HBAC rule allow_all
  [34/43]: adding entries for topology management
  [35/43]: initializing group membership
  [36/43]: adding master entry
  [37/43]: initializing domain level
  [38/43]: configuring Posix uid/gid generation
  [39/43]: adding replication acis
  [40/43]: activating sidgen plugin
  [41/43]: activating extdom plugin
  [42/43]: configuring directory to start on boot
  [43/43]: restarting directory server
Done configuring directory server (dirsrv).
Configuring Kerberos KDC (krb5kdc)
  [1/11]: adding kerberos container to the directory
  [2/11]: configuring KDC
  [3/11]: initialize kerberos container
  [4/11]: adding default ACIs
  [5/11]: creating a keytab for the directory
  [6/11]: creating a keytab for the machine
  [7/11]: adding the password extension to the directory
  [8/11]: creating anonymous principal
  [9/11]: starting the KDC
  [10/11]: configuring KDC to start on boot
  [11/11]: enable PAC ticket signature support
Done configuring Kerberos KDC (krb5kdc).
Configuring kadmin
  [1/2]: starting kadmin 
  [2/2]: configuring kadmin to start on boot
Done configuring kadmin.
Configuring ipa-custodia
  [1/5]: Making sure custodia container exists
  [2/5]: Generating ipa-custodia config file
  [3/5]: Generating ipa-custodia keys
  [4/5]: starting ipa-custodia 
  [5/5]: configuring ipa-custodia to start on boot
Done configuring ipa-custodia.
Configuring certificate server (pki-tomcatd). Estimated time: 3 minutes
  [1/32]: configuring certificate server instance
  [2/32]: stopping certificate server instance to update CS.cfg
  [3/32]: backing up CS.cfg
  [4/32]: Add ipa-pki-wait-running
Set start up timeout of pki-tomcatd service to 90 seconds
  [5/32]: secure AJP connector
  [6/32]: reindex attributes
  [7/32]: exporting Dogtag certificate store pin
  [8/32]: disabling nonces
  [9/32]: set up CRL publishing
  [10/32]: enable PKIX certificate path discovery and validation
  [11/32]: authorizing RA to modify profiles
  [12/32]: authorizing RA to manage lightweight CAs
  [13/32]: Ensure lightweight CAs container exists
  [14/32]: Enable lightweight CA monitor
  [15/32]: Ensuring backward compatibility
  [16/32]: updating IPA configuration
  [17/32]: starting certificate server instance
  [18/32]: configure certmonger for renewals
  [19/32]: requesting RA certificate from CA
  [20/32]: publishing the CA certificate
  [21/32]: adding RA agent as a trusted user
  [22/32]: configure certificate renewals
  [23/32]: Configure HTTP to proxy connections
  [24/32]: enabling CA instance
  [25/32]: importing IPA certificate profiles
  [26/32]: migrating certificate profiles to LDAP
  [27/32]: adding default CA ACL
  [28/32]: adding 'ipa' CA entry
  [29/32]: Recording random serial number state
  [30/32]: Recording HSM configuration state
  [31/32]: configuring certmonger renewal for lightweight CAs
  [32/32]: deploying ACME service
Done configuring certificate server (pki-tomcatd).
Configuring directory server (dirsrv)
  [1/3]: configuring TLS for DS instance
  [2/3]: adding CA certificate entry
  [3/3]: restarting directory server
Done configuring directory server (dirsrv).
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)
  [1/22]: stopping httpd
  [2/22]: backing up ssl.conf
  [3/22]: disabling nss.conf
  [4/22]: configuring mod_ssl certificate paths
  [5/22]: setting mod_ssl protocol list
  [6/22]: configuring mod_ssl log directory
  [7/22]: disabling mod_ssl OCSP
  [8/22]: adding URL rewriting rules
  [9/22]: configuring httpd
Nothing to do for configure_httpd_wsgi_conf
  [10/22]: setting up httpd keytab
  [11/22]: configuring Gssproxy
  [12/22]: setting up ssl
  [13/22]: configure certmonger for renewals
  [14/22]: publish CA cert
  [15/22]: clean up any existing httpd ccaches
  [16/22]: enable ccache sweep
  [17/22]: configuring SELinux for httpd
  [18/22]: create KDC proxy config
  [19/22]: enable KDC proxy
  [20/22]: starting httpd
  [21/22]: configuring httpd to start on boot
  [22/22]: enabling oddjobd
Done configuring the web interface (httpd).
Configuring Kerberos KDC (krb5kdc)
  [1/1]: installing X509 Certificate for PKINIT
Done configuring Kerberos KDC (krb5kdc).
Applying LDAP updates
Upgrading IPA:. Estimated time: 1 minute 30 seconds
  [1/10]: stopping directory server
  [2/10]: saving configuration
  [3/10]: disabling listeners
  [4/10]: enabling DS global lock
  [5/10]: disabling Schema Compat
  [6/10]: starting directory server
  [7/10]: upgrading server
  [8/10]: stopping directory server
  [9/10]: restoring configuration
  [10/10]: starting directory server
Done.
Restarting the KDC
dnssec-validation yes
Configuring DNS (named)
  [1/13]: generating rndc key file
  [2/13]: adding DNS container
  [3/13]: setting up our zone
  [4/13]: setting up reverse zone
  [5/13]: setting up our own record
  [6/13]: setting up records for other masters
  [7/13]: adding NS record to the zones
  [8/13]: setting up kerberos principal
  [9/13]: setting up LDAPI autobind
  [10/13]: setting up named.conf
created new /etc/named.conf
created named user config '/etc/named/ipa-ext.conf'
created named user config '/etc/named/ipa-options-ext.conf'
created named user config '/etc/named/ipa-logging-ext.conf'
  [11/13]: setting up server configuration
  [12/13]: configuring named to start on boot
  [13/13]: changing resolv.conf to point to ourselves
Done configuring DNS (named).
Restarting the web server to pick up resolv.conf changes
Configuring DNS key synchronization service (ipa-dnskeysyncd)
  [1/7]: checking status
  [2/7]: setting up bind-dyndb-ldap working directory
  [3/7]: setting up kerberos principal
  [4/7]: setting up SoftHSM
  [5/7]: adding DNSSEC containers
  [6/7]: creating replica keys
  [7/7]: configuring ipa-dnskeysyncd to start on boot
Done configuring DNS key synchronization service (ipa-dnskeysyncd).
Restarting ipa-dnskeysyncd
Restarting named
Updating DNS system records
Configuring SID generation
  [1/8]: adding RID bases
  [2/8]: creating samba domain object
  [3/8]: adding admin(group) SIDs
  [4/8]: updating Kerberos config
'dns_lookup_kdc' already set to 'true', nothing to do.
  [5/8]: activating sidgen task
  [6/8]: restarting Directory Server to take MS PAC and LDAP plugins changes into account
  [7/8]: adding fallback group
  [8/8]: adding SIDs to existing users and groups
This step may take considerable amount of time, please wait..
Done.
Configuring client side components
This program will set up IPA client.
Version 4.12.2

Using existing certificate '/etc/ipa/ca.crt'.
Client hostname: rhel-170-10.lab.aaronrombaut.com
Realm: LAB.AARONROMBAUT.COM
DNS Domain: lab.aaronrombaut.com
IPA Server: rhel-170-10.lab.aaronrombaut.com
BaseDN: dc=lab,dc=aaronrombaut,dc=com

Configured /etc/sssd/sssd.conf
Systemwide CA database updated.
Adding SSH public key from /etc/ssh/ssh_host_ecdsa_key.pub
Adding SSH public key from /etc/ssh/ssh_host_ed25519_key.pub
Adding SSH public key from /etc/ssh/ssh_host_rsa_key.pub
SSSD enabled
Configured /etc/openldap/ldap.conf
Configured /etc/ssh/ssh_config
Configured /etc/ssh/sshd_config.d/04-ipa.conf
Configuring lab.aaronrombaut.com as NIS domain.
Client configuration complete.
The ipa-client-install command was successful

==============================================================================
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 certificates stored in /root/cacert.p12
These files are required to create replicas. The password for these
files is the Directory Manager password
The ipa-server-install command was successful

Open a web browser and navigate to the IdM Server that was just installed.

Configure Reverse DNS Zones

Use the CIDR notation for the networks that will be in the forward lookup zone. This will allow the necessary pointer (PTR) record to be created. This is commonly referred to as a reverse lookup.

Preparing for replica server

Configure the replica server like the primary using the steps at the beginning of this post. Wait to take a snapshot until mentioned later. There are a few additional configurations that need to take place.

  • Add a DNS entry for replica server
  • NTP Service Record in DNS
  • SSH, if needed
  • /etc/hosts
  • Firewall
  • Download and install the packages

The following additional steps are required for the server to properly configure.

DNS Entry for Replica Server

NTP Service Record in DNS

Add a Service Record for _ntp._udp in the DNS Zone.

BIND Recursion

A few parameters need to be added so that BIND can provide DNS services.

/etc/named/ipa-ext.conf

acl "trusted_network" { 
  localnets;
  localhost;
  172.16.0.0/16; 
  10.10.92.0/24;
};

/etc/named/ipa-options-ext.conf

allow-recursion { trusted_network; };
allow-query-cache { trusted_network; };

Restart the named.service service.

systemctl restart named.service

NTP Configuration

Other network devices need to use NTP services. Opening the firewall is one step to allow the server to serve the service, but there is a per-service allow list that also needs to be configured.

/etc/chrony.conf

 24 # Allow NTP client access from local network.
 25 #allow 192.168.0.0/16
 26 allow all

Restart the chronyd.service service.

systemctl restart chronyd.service

Now check the system’s clock performance with chronyc tracking. I bolded important things to check.

Reference ID    : A29FC801 (time.cloudflare.com)
Stratum         : 4
Ref time (UTC)  : Mon Oct 06 13:18:02 2025
System time     : 0.000069524 seconds fast of NTP time
Last offset     : +0.000033823 seconds
RMS offset      : 0.000073869 seconds
Frequency       : 0.417 ppm slow
Residual freq   : +0.000 ppm
Skew            : 0.016 ppm
Root delay      : 0.047998678 seconds
Root dispersion : 0.001616631 seconds
Update interval : 1037.4 seconds
Leap status     : Normal

Point Replica to Primary DNS

Unless already configured to point to the primary DNS server, the DNS in /etc/resolv.conf is likely pointing to alternate DNS servers.

Use nmtui to configure the DNS server entries.

Restart the NetworkManager service.

systemctl restart NetworkManager

Install the Replica Server

To install the Replica Server, use the following commands. Make sure the password is wrapped in a single quote!

ipa-replica-install --setup-dns --forwarder 1.1.1.1 --forwarder 1.0.0.1 --setup-ca --principal admin --password '<password>'

Here is what the output looks like.

Configuring client side components
This program will set up IPA client.
Version 4.12.2

Discovery was successful!
Client hostname: rhel-170-11.lab.aaronrombaut.com
Realm: LAB.AARONROMBAUT.COM
DNS Domain: lab.aaronrombaut.com
IPA Server: rhel-170-10.lab.aaronrombaut.com
BaseDN: dc=lab,dc=aaronrombaut,dc=com

Synchronizing time
Configuration of chrony was changed by installer.
Attempting to sync time with chronyc.
Process chronyc waitsync failed to sync time!
Unable to sync time with chrony server, assuming the time is in sync. Please check that 123 UDP port is opened, and any time server is on network.
Successfully retrieved CA cert
    Subject:     CN=Certificate Authority,O=LAB.AARONROMBAUT.COM
    Issuer:      CN=Certificate Authority,O=LAB.AARONROMBAUT.COM
    Valid From:  2025-10-06 16:17:59+00:00
    Valid Until: 2045-10-06 16:17:59+00:00

Enrolled in IPA realm LAB.AARONROMBAUT.COM
Created /etc/ipa/default.conf
Configured /etc/sssd/sssd.conf
Systemwide CA database updated.
Hostname (rhel-170-11.lab.aaronrombaut.com) does not have A/AAAA record.
Missing reverse record(s) for address(es): 172.17.0.11.
Adding SSH public key from /etc/ssh/ssh_host_ecdsa_key.pub
Adding SSH public key from /etc/ssh/ssh_host_ed25519_key.pub
Adding SSH public key from /etc/ssh/ssh_host_rsa_key.pub
SSSD enabled
Configured /etc/openldap/ldap.conf
Configured /etc/ssh/ssh_config
Configured /etc/ssh/sshd_config.d/04-ipa.conf
Configuring lab.aaronrombaut.com as NIS domain.
Configured /etc/krb5.conf for IPA realm LAB.AARONROMBAUT.COM
Client configuration complete.
The ipa-client-install command was successful

Lookup failed: Preferred host rhel-170-11.lab.aaronrombaut.com does not provide DNS.
Reverse DNS resolution of address 172.17.0.11 (rhel-170-11.lab.aaronrombaut.com) failed. Clients may not function properly. Please check your DNS setup. (Note that this check queries IPA DNS directly and ignores /etc/hosts.)
Continue? [no]: yes
Checking DNS forwarders, please wait ...
Run connection check to master
Connection check OK
Disabled p11-kit-proxy
Configuring directory server (dirsrv). Estimated time: 30 seconds
  [1/40]: creating directory server instance
Validate installation settings ...
Create file system structures ...
Perform SELinux labeling ...
Create database backend: dc=lab,dc=aaronrombaut,dc=com ...
Perform post-installation tasks ...
  [2/40]: tune ldbm plugin
  [3/40]: adding default schema
  [4/40]: enabling memberof plugin
  [5/40]: enabling winsync plugin
  [6/40]: configure password logging
  [7/40]: configuring replication version plugin
  [8/40]: enabling IPA enrollment plugin
  [9/40]: configuring uniqueness plugin
  [10/40]: configuring uuid plugin
  [11/40]: configuring modrdn plugin
  [12/40]: configuring DNS plugin
  [13/40]: enabling entryUSN plugin
  [14/40]: configuring lockout plugin
  [15/40]: configuring graceperiod plugin
  [16/40]: configuring topology plugin
  [17/40]: creating indices
  [18/40]: enabling referential integrity plugin
  [19/40]: configuring certmap.conf
  [20/40]: configure new location for managed entries
  [21/40]: configure dirsrv ccache and keytab
  [22/40]: enabling SASL mapping fallback
  [23/40]: restarting directory server
  [24/40]: creating DS keytab
  [25/40]: ignore time skew for initial replication
  [26/40]: setting up initial replication
Starting replication, please wait until this has completed.
Update in progress, 7 seconds elapsed
Update succeeded

  [27/40]: prevent time skew after initial replication
  [28/40]: adding sasl mappings to the directory
  [29/40]: updating schema
  [30/40]: setting Auto Member configuration
  [31/40]: enabling S4U2Proxy delegation
  [32/40]: initializing group membership
  [33/40]: adding master entry
  [34/40]: initializing domain level
  [35/40]: configuring Posix uid/gid generation
  [36/40]: adding replication acis
  [37/40]: activating sidgen plugin
  [38/40]: activating extdom plugin
  [39/40]: configuring directory to start on boot
  [40/40]: restarting directory server
Done configuring directory server (dirsrv).
Replica DNS records could not be added on master: Insufficient access: Insufficient 'add' privilege to add the entry 'idnsname=rhel-170-11,idnsname=lab.aaronrombaut.com.,cn=dns,dc=lab,dc=aaronrombaut,dc=com'.
Configuring Kerberos KDC (krb5kdc)
  [1/6]: configuring KDC
  [2/6]: adding the password extension to the directory
  [3/6]: creating anonymous principal
  [4/6]: starting the KDC
  [5/6]: configuring KDC to start on boot
  [6/6]: enable PAC ticket signature support
Done configuring Kerberos KDC (krb5kdc).
Configuring kadmin
  [1/2]: starting kadmin 
  [2/2]: configuring kadmin to start on boot
Done configuring kadmin.
Configuring directory server (dirsrv)
  [1/3]: configuring TLS for DS instance
  [2/3]: importing CA certificates from LDAP
  [3/3]: restarting directory server
Done configuring directory server (dirsrv).
Configuring the web interface (httpd)
  [1/22]: stopping httpd
  [2/22]: backing up ssl.conf
  [3/22]: disabling nss.conf
  [4/22]: configuring mod_ssl certificate paths
  [5/22]: setting mod_ssl protocol list
  [6/22]: configuring mod_ssl log directory
  [7/22]: disabling mod_ssl OCSP
  [8/22]: adding URL rewriting rules
  [9/22]: configuring httpd
Nothing to do for configure_httpd_wsgi_conf
  [10/22]: setting up httpd keytab
  [11/22]: configuring Gssproxy
  [12/22]: setting up ssl
  [13/22]: configure certmonger for renewals
  [14/22]: publish CA cert
  [15/22]: clean up any existing httpd ccaches
  [16/22]: enable ccache sweep
  [17/22]: configuring SELinux for httpd
  [18/22]: create KDC proxy config
  [19/22]: enable KDC proxy
  [20/22]: starting httpd
  [21/22]: configuring httpd to start on boot
  [22/22]: enabling oddjobd
Done configuring the web interface (httpd).
Configuring ipa-otpd
  [1/2]: starting ipa-otpd 
  [2/2]: configuring ipa-otpd to start on boot
Done configuring ipa-otpd.
Custodia uses 'rhel-170-10.lab.aaronrombaut.com' as master peer.
Configuring ipa-custodia
  [1/4]: Generating ipa-custodia config file
  [2/4]: Generating ipa-custodia keys
  [3/4]: starting ipa-custodia 
  [4/4]: configuring ipa-custodia to start on boot
Done configuring ipa-custodia.
Configuring certificate server (pki-tomcatd). Estimated time: 3 minutes
  [1/33]: creating certificate server db
  [2/33]: ignore time skew for initial replication
  [3/33]: setting up initial replication
Starting replication, please wait until this has completed.
Update in progress, 4 seconds elapsed
Update succeeded

  [4/33]: revert time skew after initial replication
  [5/33]: creating ACIs for admin
  [6/33]: creating installation admin user
  [7/33]: configuring certificate server instance
  [8/33]: stopping certificate server instance to update CS.cfg
  [9/33]: backing up CS.cfg
  [10/33]: Add ipa-pki-wait-running
Set start up timeout of pki-tomcatd service to 90 seconds
  [11/33]: secure AJP connector
  [12/33]: reindex attributes
  [13/33]: exporting Dogtag certificate store pin
  [14/33]: disabling nonces
  [15/33]: set up CRL publishing
  [16/33]: enable PKIX certificate path discovery and validation
  [17/33]: authorizing RA to modify profiles
  [18/33]: authorizing RA to manage lightweight CAs
  [19/33]: Ensure lightweight CAs container exists
  [20/33]: Enable lightweight CA monitor
  [21/33]: Ensuring backward compatibility
  [22/33]: destroying installation admin user
  [23/33]: updating IPA configuration
  [24/33]: starting certificate server instance
  [25/33]: Finalize replication settings
  [26/33]: configure certmonger for renewals
  [27/33]: Importing RA key
  [28/33]: configure certificate renewals
  [29/33]: Configure HTTP to proxy connections
  [30/33]: enabling CA instance
  [31/33]: importing IPA certificate profiles
Lookup failed: Preferred host rhel-170-11.lab.aaronrombaut.com does not provide CA.
  [32/33]: configuring certmonger renewal for lightweight CAs
  [33/33]: deploying ACME service
Done configuring certificate server (pki-tomcatd).
Configuring Kerberos KDC (krb5kdc)
  [1/1]: installing X509 Certificate for PKINIT
Done configuring Kerberos KDC (krb5kdc).
Applying LDAP updates
Upgrading IPA:. Estimated time: 1 minute 30 seconds
  [1/10]: stopping directory server
  [2/10]: saving configuration
  [3/10]: disabling listeners
  [4/10]: enabling DS global lock
  [5/10]: disabling Schema Compat
  [6/10]: starting directory server
  [7/10]: upgrading server
  [8/10]: stopping directory server
  [9/10]: restoring configuration
  [10/10]: starting directory server
Done.
Finalize replication settings
Restarting the KDC
dnssec-validation yes
Configuring DNS (named)
  [1/9]: generating rndc key file
  [2/9]: setting up our own record
  [3/9]: adding NS record to the zones
  [4/9]: setting up kerberos principal
  [5/9]: setting up LDAPI autobind
  [6/9]: setting up named.conf
created new /etc/named.conf
created named user config '/etc/named/ipa-ext.conf'
created named user config '/etc/named/ipa-options-ext.conf'
created named user config '/etc/named/ipa-logging-ext.conf'
  [7/9]: setting up server configuration
  [8/9]: configuring named to start on boot
  [9/9]: changing resolv.conf to point to ourselves
Done configuring DNS (named).
Restarting the web server to pick up resolv.conf changes
Configuring DNS key synchronization service (ipa-dnskeysyncd)
  [1/7]: checking status
  [2/7]: setting up bind-dyndb-ldap working directory
  [3/7]: setting up kerberos principal
  [4/7]: setting up SoftHSM
  [5/7]: adding DNSSEC containers
DNSSEC container exists (step skipped)
  [6/7]: creating replica keys
  [7/7]: configuring ipa-dnskeysyncd to start on boot
Done configuring DNS key synchronization service (ipa-dnskeysyncd).
Restarting ipa-dnskeysyncd
Restarting named
Updating DNS system records

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

Configuring SID generation
  [1/7]: adding RID bases
RID bases already set, nothing to do
  [2/7]: creating samba domain object
Samba domain object already exists
  [3/7]: adding admin(group) SIDs
Admin SID already set, nothing to do
Admin group SID already set, nothing to do
  [4/7]: updating Kerberos config
'dns_lookup_kdc' already set to 'true', nothing to do.
  [5/7]: activating sidgen task
  [6/7]: restarting Directory Server to take MS PAC and LDAP plugins changes into account
  [7/7]: adding fallback group
Fallback group already set, nothing to do
Done.
The ipa-replica-install command was successful

Tasks After the Replica Installs

Set up the DNS recursion parameters as well as NTP so that they can serve their services.

Conclusion

This should now be a working Red Hat IdM installation.

Leave a Reply

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