IdM / FreeIPA
De jagfloriano.com
Identity Management (IdM / FreeIPA)
Introducción
Identity Management (IdM), basado en FreeIPA, es la solución de Red Hat para la gestión centralizada de identidades. IdM integra varios servicios en una única plataforma:
- LDAP (389 Directory Server)
- Kerberos
- DNS
- Certificados (Dogtag CA)
- Gestión de usuarios, grupos y políticas
En RHEL 9, IdM es la solución recomendada y soportada oficialmente para servicios de directorio.
Requisitos previos
- IP estática configurada
- Hostname con FQDN correcto
- Resolución de nombre funcional
- Sincronización horaria activa (NTP)
- Acceso a repositorios oficiales de RHEL
Ejemplo:
192.168.1.81 nodo1.jagfloriano.com node1
Preparación del sistema
Comprobar hostname y FQDN:
[root@nodo1 ~]# hostname
nodo1
[root@nodo1 ~]# hostname -f
nodo1.jagfloriano.com
[root@nodo1 ~]# hostnamectl
Static hostname: nodo1
Icon name: computer-vm
Chassis: vm 🖴
Machine ID: 20ff935e15e14490a6e182f1a7979010
Boot ID: daaaf7f2b9104421820d256e95a711c3
Virtualization: oracle
Operating System: Red Hat Enterprise Linux 9.7 (Plow)
CPE OS Name: cpe:/o:redhat:enterprise_linux:9::baseos
Kernel: Linux 5.14.0-570.12.1.el9_6.x86_64
Architecture: x86-64
Firmware Version: VirtualBox
Comprobar resolución de nombre:
[root@nodo1 ~]# getent hosts nodo1
fe80::a00:27ff:fef3:3c51 nodo1
Verificar sincronización horaria:
[root@nodo1 ~]# timedatectl
Local time: Tue 2026-02-03 09:19:15 CET
Universal time: Tue 2026-02-03 08:19:15 UTC
RTC time: Tue 2026-02-03 08:19:15
Time zone: Europe/Madrid (CET, +0100)
System clock synchronized: yes
NTP service: active
RTC in local TZ: no
Instalación de paquetes IdM
Instalar el grupo de paquetes del servidor IdM:
dnf install -y ipa-server ipa-server-dns
Verificar instalación:
[root@nodo1 ~]# rpm -qa | grep ipa
python3-iniparse-0.4-45.el9.noarch
libipa_hbac-2.9.7-4.el9_7.1.x86_64
sssd-ipa-2.9.7-4.el9_7.1.x86_64
device-mapper-multipath-libs-0.8.7-39.el9_7.1.x86_64
device-mapper-multipath-0.8.7-39.el9_7.1.x86_64
ipa-client-common-4.12.2-22.el9_7.1.noarch
python3-libipa_hbac-2.9.7-4.el9_7.1.x86_64
ipa-selinux-4.12.2-22.el9_7.1.noarch
ipa-common-4.12.2-22.el9_7.1.noarch
ipa-healthcheck-core-0.16-9.el9.noarch
redhat-logos-ipa-90.5-1.el9_6.1.noarch
ipa-server-common-4.12.2-22.el9_7.1.noarch
python3-ipalib-4.12.2-22.el9_7.1.noarch
python3-ipaclient-4.12.2-22.el9_7.1.noarch
ipa-client-4.12.2-22.el9_7.1.x86_64
python3-ipaserver-4.12.2-22.el9_7.1.noarch
ipa-server-4.12.2-22.el9_7.1.x86_64
ipa-server-dns-4.12.2-22.el9_7.1.noarch
Configuración inicial del servidor IdM
La configuración inicial se realiza mediante el asistente `ipa-server-install`.
Ejecutar el instalador:
ipa-server-install
Durante el asistente se solicitará:
- Nombre de dominio (ej: jagfloriano.com)
- Realm Kerberos (ej: JAGFLORIANO.COM)
- Contraseña del usuario admin
- Configuración del DNS integrado
- Reenvíos DNS (forwarders)
- Confirmación de instalación
Valores recomendados:
- Usar DNS integrado
- Configurar al menos un DNS forwarder
- Mantener el realm en mayúsculas
[root@nodo1 ~]# 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]:
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 [nodo1.jagfloriano.com]:
The domain name has been determined based on the host name.
Please confirm the domain name [jagfloriano.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 [JAGFLORIANO.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):
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 [JAGFLORIANO]:
Do you want to configure chrony with NTP server or pool address? [no]:
The IPA Master Server will be configured with:
Hostname: nodo1.jagfloriano.com
IP address(es): 192.168.1.81
Domain name: jagfloriano.com
Realm name: JAGFLORIANO.COM
The CA will be configured with:
Subject DN: CN=Certificate Authority,O=JAGFLORIANO.COM
Subject base: O=JAGFLORIANO.COM
Chaining: self-signed
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.
Disabled p11-kit-proxy
Synchronizing time
No SRV records of NTP servers found and no NTP server or pool address was provided.
Using default chrony configuration.
Attempting to sync time with chronyc.
Time synchronization was successful.
Configuring directory server (dirsrv). Estimated time: 30 seconds
Arranque y verificación
Comprobar servicios IdM:
ipactl status
Comprobar acceso administrativo:
kinit admin
Ver información del dominio:
ipa domain-show
---
Acceso web
IdM proporciona una interfaz web de administración.
URL:
https://node1.jagfloriano.com
Acceder con el usuario **admin**.
---
Firewall
Durante la instalación, IdM configura automáticamente el firewall. Puertos principales utilizados:
- 389/TCP (LDAP)
- 636/TCP (LDAPS)
- 88/TCP y UDP (Kerberos)
- 464/TCP y UDP (Kerberos)
- 443/TCP (Web UI)
- 53/TCP y UDP (DNS, si se habilita)
---
Resultado de la instalación
Al finalizar la instalación:
- IdM está operativo
- LDAP, Kerberos y DNS funcionan de forma integrada
- El sistema está listo para crear usuarios y grupos
- Los clientes pueden unirse al dominio
