Como construir nuestro propio laboratorio de practicas FreeIPA

Como ya habia comentado en otro articulo, es muy importante tener su lab listo para practicar. Pero siempre vamos a necesitar un servidor que nos permita practicar los objetivos referentes a LDAP y autofs, por ejemplo.

Realizar esta configuracion puede hacerlo sentir desanimado para continuar, pero aqui les voy a explicar como lograrlo de la forma mas simple posible.

La configuracion que vamos a realizar es basada en FreeIPA, el cual es una integracion de un servidor de directorios, kerberos, ntp, dns, sssd y otros.

Para comenzar con nuestra configuarion vamos a partir de los siguiente:

Servidor: class2.lab.local.com 192.168.4.100
RHEL version: Red Hat Enterprise Linux Server release 7.3 (Maipo)

Pero antes de comenzar a instalar los paquetes necesarios vamos a realizar algunos cambios en nuestro servidor:

[root@class2 ~]# cat /etc/resolv.conf
# Generated by NetworkManager
search lab.local.com
nameserver 192.168.4.100
[root@class2 ~]#
[root@class2 ~]# cat /etc/hosts
127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
192.168.4.100 class2.lab.local.com class2
[root@class2 ~]#

Ademas de estos cambios debe asegurarse de que su red esta configurada con una ip estatica. Ya teniendo estos datos correctos podemos comenzar con la instalacion de los paquetes necesarios. Es importante que tenga su repositorio local ya configurado. Es importante aclarar el el archivo resolf.conf no deben de editarlo manualmente, para esto pueden utilizar el comando “nmcli” o bien la utilidad grafica de configuracion de la red.

[root@class2 ~]# yum -y install ipa-server bind-dyndb-ldap ipa-server-dns
Loaded plugins: langpacks, product-id, search-disabled-repos, subscription-manager
This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.
Resolving Dependencies
--> Running transaction check
---> Package bind-dyndb-ldap.x86_64 0:10.0-5.el7 will be installed
--> Processing Dependency: bind >= 32:9.9.0-1 for package: bind-dyndb-ldap-10.0-5.el7.x86_64
---> Package ipa-server.x86_64 0:4.4.0-12.el7 will be installed
--> Processing Dependency: ipa-admintools = 4.4.0-12.el7 for package: ipa-server-4.4.0-12.el7.x86_64

...
...

Estos paquetes que estamos instalando van hacer el trabajo sucio de instalar todo lo que necesitamos. Una vez ya terminado la instalacion pues ya vamos a proceder con la configuracion, la cual es muy simple. Para esto vamos a ejecutar el comando “ipa-server-install”.

Es muy importante leer los datos que vamos a ir cambbiando de acuerdo a nuestro sistema, porque este comando lo que hace es seguir una seria de procedimientos ayudandonos a la configuracion del server FreeIPA.

[root@class2 ~]# 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.

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 [class2.lab.local.com]:

Warning: skipping DNS resolution of host class2.lab.local.com
The domain name has been determined based on the host name.

Please confirm the domain name [lab.local.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.LOCAL.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
Password (confirm): password

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
Password (confirm): password

Checking DNS domain lab.local.com., please wait ...
Do you want to configure DNS forwarders? [yes]: yes
Following DNS servers are configured in /etc/resolv.conf: 192.168.4.100
Do you want to configure these servers as DNS forwarders? [yes]: no
Enter an IP address for a DNS forwarder, or press Enter to skip: 8.8.8.8
DNS forwarder 8.8.8.8 added. You may add another.
Enter an IP address for a DNS forwarder, or press Enter to skip:
Checking DNS forwarders, please wait ...
Do you want to search for missing reverse zones? [yes]:

The IPA Master Server will be configured with:
Hostname: class2.lab.local.com
IP address(es): 192.168.4.100
Domain name: lab.local.com
Realm name: LAB.LOCAL.COM

BIND DNS server will be configured to serve IPA domain with:
Forwarders: 8.8.8.8
Forward policy: only
Reverse zone(s): No reverse zone

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

Hasta este punto como pueden ver ya tenemos la configracion necesaria, solo tenemos que escribir “yes” y presionar ENTER para finalizar. La aplicacion de la configuracion puede tardar varios minutos, por lo que le recomiendo que sea paciente. Aclaro que la parte mas complicada es la de definicion del “DNS forwarder”. Pero para propositos de este servidor no es muy importante, o al menos eso pienso yo.

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 (dirsrv). Estimated time: 1 minute
[1/47]: creating directory server user
[2/47]: creating directory server instance
[3/47]: updating configuration in dse.ldif
[4/47]: restarting directory server
[5/47]: adding default schema
[6/47]: enabling memberof plugin
[7/47]: enabling winsync plugin
[8/47]: configuring replication version plugin
[9/47]: enabling IPA enrollment plugin
[10/47]: enabling ldapi
[11/47]: configuring uniqueness plugin
[12/47]: configuring uuid plugin
[13/47]: configuring modrdn plugin
[14/47]: configuring DNS plugin
[15/47]: enabling entryUSN plugin
[16/47]: configuring lockout plugin
[17/47]: configuring topology plugin
[18/47]: creating indices
[19/47]: enabling referential integrity plugin
[20/47]: configuring certmap.conf
[21/47]: configure autobind for root
[22/47]: configure new location for managed entries
[23/47]: configure dirsrv ccache
[24/47]: enabling SASL mapping fallback
[25/47]: restarting directory server
[26/47]: adding sasl mappings to the directory
[27/47]: adding default layout
[28/47]: adding delegation layout
[29/47]: creating container for managed entries
[30/47]: configuring user private groups
[31/47]: configuring netgroups from hostgroups
[32/47]: creating default Sudo bind user
[33/47]: creating default Auto Member layout
[34/47]: adding range check plugin
[35/47]: creating default HBAC rule allow_all
[36/47]: adding sasl mappings to the directory
[37/47]: adding entries for topology management
[38/47]: initializing group membership
[39/47]: adding master entry
[40/47]: initializing domain level
[41/47]: configuring Posix uid/gid generation
[42/47]: adding replication acis
[43/47]: enabling compatibility plugin
[44/47]: activating sidgen plugin
[45/47]: activating extdom plugin
[46/47]: tuning directory server
[47/47]: configuring directory to start on boot
Done configuring directory server (dirsrv).
Configuring certificate server (pki-tomcatd). Estimated time: 3 minutes 30 seconds
[1/31]: creating certificate server user
[2/31]: configuring certificate server instance
[3/31]: stopping certificate server instance to update CS.cfg
[4/31]: backing up CS.cfg
[5/31]: disabling nonces
[6/31]: set up CRL publishing
[7/31]: enable PKIX certificate path discovery and validation
[8/31]: starting certificate server instance
[9/31]: creating RA agent certificate database
[10/31]: importing CA chain to RA certificate database
[11/31]: fixing RA database permissions
[12/31]: setting up signing cert profile
[13/31]: setting audit signing renewal to 2 years
[14/31]: restarting certificate server
[15/31]: requesting RA certificate from CA
[16/31]: issuing RA agent certificate
[17/31]: adding RA agent as a trusted user
[18/31]: authorizing RA to modify profiles
[19/31]: authorizing RA to manage lightweight CAs
[20/31]: Ensure lightweight CAs container exists
[21/31]: configure certmonger for renewals
[22/31]: configure certificate renewals
[23/31]: configure RA certificate renewal
[24/31]: configure Server-Cert certificate renewal
[25/31]: Configure HTTP to proxy connections
[26/31]: restarting certificate server
[27/31]: migrating certificate profiles to LDAP
[28/31]: importing IPA certificate profiles
[29/31]: adding default CA ACL
[30/31]: adding 'ipa' CA entry
[31/31]: updating IPA configuration
Done configuring certificate server (pki-tomcatd).
Configuring directory server (dirsrv). Estimated time: 10 seconds
[1/3]: configuring ssl for ds instance
[2/3]: restarting directory server
[3/3]: adding CA certificate entry
Done configuring directory server (dirsrv).
Configuring Kerberos KDC (krb5kdc). Estimated time: 30 seconds
[1/9]: adding kerberos container to the directory
[2/9]: configuring KDC
[3/9]: initialize kerberos container
[4/9]: adding default ACIs
[5/9]: creating a keytab for the directory
[6/9]: creating a keytab for the machine
[7/9]: adding the password extension to the directory
[8/9]: starting the KDC
[9/9]: 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 ipa-custodia
[1/5]: Generating ipa-custodia config file
[2/5]: Making sure custodia container exists
[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 the web interface (httpd). Estimated time: 1 minute
[1/21]: setting mod_nss port to 443
[2/21]: setting mod_nss cipher suite
[3/21]: setting mod_nss protocol list to TLSv1.0 - TLSv1.2
[4/21]: setting mod_nss password file
[5/21]: enabling mod_nss renegotiate
[6/21]: adding URL rewriting rules
[7/21]: configuring httpd
[8/21]: configure certmonger for renewals
[9/21]: setting up httpd keytab
[10/21]: setting up ssl
[11/21]: importing CA certificates from LDAP
[12/21]: setting up browser autoconfig
[13/21]: publish CA cert
[14/21]: clean up any existing httpd ccache
[15/21]: configuring SELinux for httpd
[16/21]: create KDC proxy user
[17/21]: create KDC proxy config
[18/21]: enable KDC proxy
[19/21]: restarting httpd
[20/21]: configuring httpd to start on boot
[21/21]: enabling oddjobd
Done configuring the web interface (httpd).
Applying LDAP updates
Upgrading IPA:
[1/9]: stopping directory server
[2/9]: saving configuration
[3/9]: disabling listeners
[4/9]: enabling DS global lock
[5/9]: starting directory server
[6/9]: upgrading server
[7/9]: stopping directory server
[8/9]: restoring configuration
[9/9]: starting directory server
Done.
Restarting the directory server
Restarting the KDC
Configuring DNS (named)
[1/11]: generating rndc key file
[2/11]: adding DNS container
[3/11]: setting up our zone
[4/11]: setting up our own record
[5/11]: setting up records for other masters
[6/11]: adding NS record to the zones
[7/11]: setting up kerberos principal
[8/11]: setting up named.conf
[9/11]: setting up server configuration
[10/11]: configuring named to start on boot
[11/11]: changing resolv.conf to point to ourselves
Done configuring DNS (named).
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
Restarting the web server
Configuring client side components
Using existing certificate '/etc/ipa/ca.crt'.
Client hostname: class2.lab.local.com
Realm: LAB.LOCAL.COM
DNS Domain: lab.local.com
IPA Server: class2.lab.local.com
BaseDN: dc=lab,dc=local,dc=com

Skipping synchronizing time with NTP server.
New SSSD config will be created
Configured sudoers in /etc/nsswitch.conf
Configured /etc/sssd/sssd.conf
trying https://class2.lab.local.com/ipa/json
Forwarding 'ping' to json server 'https://class2.lab.local.com/ipa/json'
Forwarding 'ca_is_enabled' to json server 'https://class2.lab.local.com/ipa/json'
Systemwide CA database updated.
Adding SSH public key from /etc/ssh/ssh_host_rsa_key.pub
Adding SSH public key from /etc/ssh/ssh_host_ecdsa_key.pub
Adding SSH public key from /etc/ssh/ssh_host_ed25519_key.pub
Forwarding 'host_mod' to json server 'https://class2.lab.local.com/ipa/json'
SSSD enabled
Configured /etc/openldap/ldap.conf
Configured /etc/ssh/ssh_config
Configured /etc/ssh/sshd_config
Configuring lab.local.com as NIS domain.
Client configuration complete.

==============================================================================
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
[root@class2 ~]#

Despues de esto ya podemos proseguir con los siguientes cambios.

[root@class2 ~]# for i in http https ldap ldaps kerberos kpasswd dns ntp; do firewall-cmd --permanent --add-service $i; done
success
success
success
success
success
success
success
success
[root@class2 ~]# firewall-cmd --reload
success
[root@class2 ~]#

Hasta este punto ya tenemos nuestro FreeIPA funcional. Entonces podemos verificarlo accediendo a la url: https://class2.lab.local.com

Ahora vamos a preparar el servidor para la autenticacion de usuarios:

root@class2 ~]# yum install -y vsftpd
Loaded plugins: langpacks, product-id, search-disabled-repos, subscription-manager
This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.
Resolving Dependencies
--> Running transaction check
---> Package vsftpd.x86_64 0:3.0.2-21.el7 will be installed
--> Finished Dependency Resolution

Dependencies Resolved

========================================================================================================================================
Package Arch Version Repository Size
========================================================================================================================================
Installing:
vsftpd x86_64 3.0.2-21.el7 OS 169 k

Transaction Summary
========================================================================================================================================
Install 1 Package

Total download size: 169 k
Installed size: 348 k
Downloading packages:
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
Installing : vsftpd-3.0.2-21.el7.x86_64 1/1
Verifying : vsftpd-3.0.2-21.el7.x86_64 1/1

Installed:
vsftpd.x86_64 0:3.0.2-21.el7

Complete!
[root@class2 ~]# systemctl enable vsftpd; systemctl start vsftpd
Created symlink from /etc/systemd/system/multi-user.target.wants/vsftpd.service to /usr/lib/systemd/system/vsftpd.service.
[root@class2 ~]# cp /etc/ipa/ca.crt /var/ftp/pub
[root@class2 ~]# firewall-cmd --permanent --add-service ftp; firewall-cmd --reload
success
success
[root@class2 ~]#

Lo que hicimos fue instalar el servicio ftp, y copiamos el ca.crt para el ftp, para que todos tengn acceso. Esto lo podemos verificar de la siguiente forma:

curl ftp://class2.lab.local.com/pub/ca.crt

O bien verificando que tiene permisos de lectura:

[root@class2 ~]# ls -ls /var/ftp/pub/ca.crt
4 -r--r--r--. 1 root root 1317 Jun 20 10:34 /var/ftp/pub/ca.crt
[root@class2 ~]#

Ahora debemos adentrarnos a la configuracion del servicio “NFS” para exportar los directorios de los usuarios ldap que aun no hemos creado.

[root@class2 ~]# yum install nfs-utils
Loaded plugins: langpacks, product-id, search-disabled-repos, subscription-manager
This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.
Package 1:nfs-utils-1.3.0-0.33.el7.x86_64 already installed and latest version
Nothing to do
[root@class2 ~]# systemctl enable rpcbind ; systemctl enable nfs-server
Created symlink from /etc/systemd/system/multi-user.target.wants/nfs-server.service to /usr/lib/systemd/system/nfs-server.service.
[root@class2 ~]# systemctl start rpcbind ; systemctl start nfs-server
[root@class2 ~]# mkdir /home/ldap
[root@class2 ~]# echo "/home/ldap *(rw)" >> /etc/exports
[root@class2 ~]# exportfs -vr
exporting *:/home/ldap
[root@class2 ~]#

Ahora vamos a verificar que podamos ver esto sistema de archivos desde otra maquina virtual.

Pero antes no se olviden de abrir el firewall para el servcio “NFS”

[root@class2 ~]# firewall-cmd --permanent --add-service=mountd
success
[root@class2 ~]# firewall-cmd --permanent --add-service=rpc-bind
success
[root@class2 ~]# firewall-cmd --permanent --add-service=nfs
success
[root@class2 ~]# firewall-cmd --reload
success
[root@class2 ~]#

Y entonces desde la maquina virtual cliente ejecutamos lo siguiente:

[root@class ~]# showmount -e class2.lab.local.com
Export list for class2.lab.local.com:
/home/ldap *
[root@class ~]#

De esta forma ya podemos comenzar a crear los usuarios en el servidor ldap. Vamos a hacerlo via cli, ya que de esta forma es mucho mas simple, pero tambien puede hacerlo a travez de la web “https://class2.lab.local.com”

Primero debemos abrir un “kerberos ticket”, y entonces proceder a crear los usuarios.

[root@class2 ~]# kinit admin
Password for admin@LAB.LOCAL.COM:
[root@class2 ~]#

De esta forma ya tenemos abierto un ticket para comenzar a trabajar con los usuarios:

[root@class2 ~]# ipa user-add ldapuser1 --first=ldapuser1 --last=user1 --email=ldapuser1@lab.local.com --homedir=/home/ldap/ldapuser1
----------------------
Added user "ldapuser1"
----------------------
User login: ldapuser1
First name: ldapuser1
Last name: user1
Full name: ldapuser1 user1
Display name: ldapuser1 user1
Initials: lu
Home directory: /home/ldap/ldapuser1
GECOS: ldapuser1 user1
Login shell: /bin/sh
Principal name: ldapuser1@LAB.LOCAL.COM
Principal alias: ldapuser1@LAB.LOCAL.COM
Email address: ldapuser1@lab.local.com
UID: 227600001
GID: 227600001
Password: False
Member of groups: ipausers
Kerberos keys available: False
[root@class2 ~]# ipa user-add ldapuser2 --first=ldapuser2 --last=user2 --email=ldapuser2@lab.local.com --homedir=/home/ldap/ldapuser2
----------------------
Added user "ldapuser2"
----------------------
User login: ldapuser2
First name: ldapuser2
Last name: user2
Full name: ldapuser2 user2
Display name: ldapuser2 user2
Initials: lu
Home directory: /home/ldap/ldapuser2
GECOS: ldapuser2 user2
Login shell: /bin/sh
Principal name: ldapuser2@LAB.LOCAL.COM
Principal alias: ldapuser2@LAB.LOCAL.COM
Email address: ldapuser2@lab.local.com
UID: 227600003
GID: 227600003
Password: False
Member of groups: ipausers
Kerberos keys available: False
[root@class2 ~]# ipa user-add ldapuser3 --first=ldapuser3 --last=user3 --email=ldapuser3@lab.local.com --homedir=/home/ldap/ldapuser3
----------------------
Added user "ldapuser3"
----------------------
User login: ldapuser3
First name: ldapuser3
Last name: user3
Full name: ldapuser3 user3
Display name: ldapuser3 user3
Initials: lu
Home directory: /home/ldap/ldapuser3
GECOS: ldapuser3 user3
Login shell: /bin/sh
Principal name: ldapuser3@LAB.LOCAL.COM
Principal alias: ldapuser3@LAB.LOCAL.COM
Email address: ldapuser3@lab.local.com
UID: 227600004
GID: 227600004
Password: False
Member of groups: ipausers
Kerberos keys available: False
[root@class2 ~]#

Solo he creado tres usuarios, esto lo puede comprobar en la web. Pero no se olviden de establecer una clave para estos usuarios.

Tambien pueden hacer el cambio en la configuracion de FreeIPA para que el directorio de los usuarios este definido en /home/ldap automaticamente para no tener que especificar el “–homedir” tal como muestro en la siguiente imagen

Y entonces cuando agregan otro usuario no es necesario especificar el “–homedir”

[root@class2 ~]# ipa user-add ldapuser4 --first=ldapuser4 --last=user4 --email=ldapuser4@lab.local.com
----------------------
Added user "ldapuser4"
----------------------
User login: ldapuser4
First name: ldapuser4
Last name: user4
Full name: ldapuser4 user4
Display name: ldapuser4 user4
Initials: lu
Home directory: /home/ldap/ldapuser4
GECOS: ldapuser4 user4
Login shell: /bin/sh
Principal name: ldapuser4@LAB.LOCAL.COM
Principal alias: ldapuser4@LAB.LOCAL.COM
Email address: ldapuser4@lab.local.com
UID: 227600005
GID: 227600005
Password: False
Member of groups: ipausers
Kerberos keys available: False
[root@class2 ~]#

Ahora para establecer la clave de estos usuarios vamos a utilizar el siguiente comando:

[root@class2 ~]# for i in {1..4}; do ipa passwd ldapuser$i; done
New Password: password
Enter New Password again to verify:password
----------------------------------------------
Changed password for "ldapuser1@LAB.LOCAL.COM"
----------------------------------------------
New Password:password
Enter New Password again to verify:password
----------------------------------------------
Changed password for "ldapuser2@LAB.LOCAL.COM"
----------------------------------------------
New Password:password
Enter New Password again to verify:password
----------------------------------------------
Changed password for "ldapuser3@LAB.LOCAL.COM"
----------------------------------------------
New Password:password
Enter New Password again to verify:password
----------------------------------------------
Changed password for "ldapuser4@LAB.LOCAL.COM"
----------------------------------------------
[root@class2 ~]#

Como ven ya quedo todo en configurado y listo para la verificacion. Pero no antes de crear los directorios en el servidor para que cuando intentemos montarlos via autofs no tengamos problemas:

[root@class2 ~ ]# cd /home/ldap/
[root@class2 ldap]# ll
total 0
[root@class2 ldap]# mkdir ldapuser{1..4}
[root@class2 ldap]# ll
total 0
drwxr-xr-x. 2 root root 6 Jun 20 12:34 ldapuser1
drwxr-xr-x. 2 root root 6 Jun 20 12:34 ldapuser2
drwxr-xr-x. 2 root root 6 Jun 20 12:34 ldapuser3
drwxr-xr-x. 2 root root 6 Jun 20 12:34 ldapuser4

Y cambiar el propietario segun corresponda a cada usuario:

[root@class2 ldap]# chown ldapuser1 ldapuser1
[root@class2 ldap]# chown ldapuser2 ldapuser2
[root@class2 ldap]# chown ldapuser3 ldapuser3
[root@class2 ldap]# chown ldapuser4 ldapuser4
[root@class2 ldap]# ll
total 0
drwxr-xr-x. 2 ldapuser1 root 6 Jun 20 12:34 ldapuser1
drwxr-xr-x. 2 ldapuser2 root 6 Jun 20 12:34 ldapuser2
drwxr-xr-x. 2 ldapuser3 root 6 Jun 20 12:34 ldapuser3
drwxr-xr-x. 2 ldapuser4 root 6 Jun 20 12:34 ldapuser4
[root@class2 ldap]#

Tambien pueden verificar el estado de los servicios que corren en FreeIPA con el siguiente comando:

[root@class2 ~]# ipactl status
Directory Service: RUNNING
krb5kdc Service: RUNNING
kadmin Service: RUNNING
named Service: RUNNING
ipa_memcached Service: RUNNING
httpd Service: RUNNING
ipa-custodia Service: RUNNING
ntpd Service: RUNNING
pki-tomcatd Service: RUNNING
ipa-otpd Service: RUNNING
ipa-dnskeysyncd Service: RUNNING
ipa: INFO: The ipactl command was successful
[root@class2 ~]#

Para las verificaciones solo siga el siguiente enlace en donde explico como hacerlo, LDAP y autofs

Espero que este material les sea de ayuda en la configuracion de su propio servidor FreeIPA. Pero no se olviden de crearle una instantanea o “snapshot” para tener un respaldo si se realiza un cambio no deseado en el servidor.

Leave a Reply

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