Chapter 20. Preparing the system for an IdM replica installation
The following links list the requirements to install an RHEL Identity Management (IdM) replica. Before the installation, make sure your system meets these requirements.
Authorize the target system for enrollment into the IdM domain. For more information, see one of the following sections that best fits your needs:
Additional resources
20.1. Replica version requirements
IdM replicas must be running the same major version of RHEL and the same or later version of IdM as other IdM servers. This ensures that configuration can be properly copied from the server to the replica.
20.2. Methods for displaying IdM software version
You can display the IdM version number with:
- The IdM WebUI
-
ipa
commands -
rpm
commands
- Displaying version through the WebUI
In the IdM WebUI, the software version can be displayed by choosing
About
from the username menu at the upper-right.- Displaying version with
ipa
commands From the command line, use the
ipa --version
command.ipa --version
[root@server ~]# ipa --version VERSION: 4.8.0, API_VERSION: 2.233
Copy to Clipboard Copied! - Displaying version with
rpm
commands If IdM services are not operating properly, you can use the
rpm
utility to determine the version number of theipa-server
package that is currently installed.rpm -q ipa-server
[root@server ~]# rpm -q ipa-server ipa-server-4.8.0-11.module+el8.1.0+4247+9f3fd721.x86_64
Copy to Clipboard Copied!
20.3. Authorizing the installation of a replica on an IdM client
When installing a replica on an existing RHEL Identity Management (IdM) client by running the ipa-replica-install
utility, choose Method 1 or Method 2 below to authorize the replica installation. Choose Method 1 if one of the following applies:
- You want a senior system administrator to perform the initial part of the procedure and a junior administrator to perform the rest.
- You want to automate your replica installation.
- Method 1: the
ipaservers
host group Log in to any IdM host as IdM admin:
kinit admin
$ kinit admin
Copy to Clipboard Copied! Add the client machine to the
ipaservers
host group:ipa hostgroup-add-member ipaservers --hosts client.example.com
$ ipa hostgroup-add-member ipaservers --hosts client.example.com Host-group: ipaservers Description: IPA server hosts Member hosts: server.example.com, client.example.com ------------------------- Number of members added 1 -------------------------
Copy to Clipboard Copied!
NoteMembership in the
ipaservers
group grants the machine elevated privileges similar to the administrator’s credentials. Therefore, in the next step, theipa-replica-install
utility can be run on the host successfully by a junior system administrator.- Method 2: a privileged user’s credentials
Choose one of the following methods to authorize the replica installation by providing a privileged user’s credentials:
-
Let RHEL Identity Management (IdM) prompt you for the credentials interactively after you start the
ipa-replica-install
utility. This is the default behavior. Log in to the client as a privileged user immediately before running the
ipa-replica-install
utility. The default privileged user isadmin
:kinit admin
$ kinit admin
Copy to Clipboard Copied!
-
Let RHEL Identity Management (IdM) prompt you for the credentials interactively after you start the
20.4. Authorizing the installation of a replica on a system that is not enrolled into IdM
When installing a replica on a system that is not enrolled in the RHEL Identity Management (IdM) domain, the ipa-replica-install
utility first enrolls the system as a client and then installs the replica components. For this scenario, choose Method 1 or Method 2 below to authorize the replica installation. Choose Method 1 if one of the following applies:
- You want a senior system administrator to perform the initial part of the procedure and a junior administrator to perform the rest.
- You want to automate your replica installation.
- Method 1: a random password generated on an IdM server
Enter the following commands on any server in the domain:
Log in as the administrator.
kinit admin
$ kinit admin
Copy to Clipboard Copied! Add the external system as an IdM host. Use the
--random
option with theipa host-add
command to generate a random one-time password to be used for the subsequent replica installation.ipa host-add replica.example.com --random
$ ipa host-add replica.example.com --random -------------------------------------------------- Added host "replica.example.com" -------------------------------------------------- Host name: replica.example.com Random password: W5YpARl=7M.n Password: True Keytab: False Managed by: server.example.com
Copy to Clipboard Copied! The generated password will become invalid after you use it to enroll the machine into the IdM domain. It will be replaced with a proper host keytab after the enrollment is finished.
Add the system to the
ipaservers
host group.ipa hostgroup-add-member ipaservers --hosts replica.example.com
$ ipa hostgroup-add-member ipaservers --hosts replica.example.com Host-group: ipaservers Description: IPA server hosts Member hosts: server.example.com, replica.example.com ------------------------- Number of members added 1 -------------------------
Copy to Clipboard Copied!
NoteMembership in the
ipaservers
group grants the machine elevated privileges similar to the administrator’s credentials. Therefore, in the next step, theipa-replica-install
utility can be run on the host successfully by a junior system administrator that provides the generated random password.- Method 2: a privileged user’s credentials
Using this method, you authorize the replica installation by providing a privileged user’s credentials. The default privileged user is
admin
.No action is required prior to running the IdM replica installation utility. Add the principal name and password options (
--principal admin --admin-password password
) to theipa-replica-install
command directly during the installation.