Procédure FREEIPA un Contrôleur de domaine sous Linux.
FreeIPA réuni un serveur LDAP (389), l’authentification KERBEROS, le serveur WEB Apache ainsi que Python pour la gestion et l’interface Web, DogTag pour l’intégration des certificats, le serveur DNS BIND, SAMBA pour l’intégration à l’Active Directory Microsoft, par le biais de la Forêt de confiance croisé.
Mais aussi l’authentification des utilisateurs SSSD, ainsi que la double authentification par OTP (One Time Password) ajoutant un code unique accessible pendant une durée limité à configurer, en plus du mot de passe qui demandera parfois une configuration particulière pour être disponible (en cours de recherche sur le sujet. Il vous faudra un logiciel en plus pour avoir accès à ce code à la demande (Exemple : FreeOTP+ disponible sur F-droid)
Le serveur est basé sur la netinstall de Fedora, actuellement en version 28. Si vous partez d’une version ‘WorkStation’, il faut savoir que le compte ‘root’ est désactivé par défaut. Je vous laisse chercher la solution pour l’activer, sinon il faudra utiliser la commande ‘sudo’ avec les droits d’administrateur pour votre utilisateur.
Je vous conseil d’avoir une machine avec ce minimum requis histoire d’éviter des problèmes avec LDAP :
- 2 cpu ou vcpu (virtual cpu)
- 2Go de mémoire
- Espace disque de 30Go
Pour les besoins de la documentation, l’infrastructure suivante est mise en place :
- 1 Serveur Proxy simple sous CentOS 7.5
- 1 machine de rebond sous Fedora 28 plasma 5
- 1 Serveur FreeIPA sous Fedora 28
- 1 Serveur de réplication FreeIPA aussi sous Fedora 28
- 1 Serveur Ansible sous Fedora 28, qui servira pour la configuration et les opérations centralisé
- 2 clients simple (1 vcpu + 512Mo de RAM)
- 1 Serveur de stockage (1vcpu + 1Go de RAM) avec trois espaces disques en RAID 5 de 100Go chaqu’un
- 1 Serveur Katello/Foreman sous CentOS 7.5 pour gérer le parc (mises à jours, configuration, déploiements, inventaire…).
Je vais commencer donc par le premier FreeIPA et les clients, le restant sera documenté par la suite au fur et à mesure.
Ici on se connectera en ‘root’ par défaut :
Domaine :
testipa.local
Serveur :
ipatest.testipa.local
IP et DNS :
10.0.2.30/24 est son propre DNS.
La première étape est de s’assurer que son serveur est bien à jour selon la politique de mise à jour choisi.
Pour les besoins de cette doc, je partirai d’une installation vierge sans fioriture de base. Le serveur sera mis à jours régulièrement (une fois par semaine).
Pour commencer on s’assure que les mises à jours sont effectué à l’aide de la commande ‘DNF’ :
dnf clean all && dnf upgrade -y
Si vous utilisez centos ou redhat c’est la commande YUM qu’il faut utiliser :
yum clean all && yum update -y
On rebootera le serveur, surtout si le noyau et la glibc sont mis à jours :
reboot
Voici la liste des paquets disponible :
[root@ipatest ~]# dnf list *freeipa*
Ou
yum list *freeipa*
Dernière vérification de l’expiration des métadonnées effectuée il y a 0:12:40 le sam. 07 juil. 2018 08:02:39 EDT.
Paquets disponibles :
freeipa-client.x86_64
freeipa-client-common.noarch
freeipa-common.noarch
freeipa-desktop-profile.noarch
freeipa-desktop-profile-common.noarch
freeipa-python-compat.noarch
freeipa-server.x86_64
freeipa-server-common.noarch
freeipa-server-dns.noarch
freeipa-server-trust-ad.x86_64
Pour commencer nous aurons besoin d’installer les paquets suivant :
freeipa-server.x86_64
freeipa-server-dns.noarch
freeipa-common.noarch
Je reviendrai sur le reste selon les besoins de la documentation.
On installe les paquets :
dnf install freeipa-server.x86_64 freeipa-server-dns.noarch freeipa-common.noarch
Ou
yum install ...
On s’assure que notre nom d’hôte est bien celui choisi :
hostname
Ici
ipatest.testipa.local
On ajoute l’ip du serveur dans /etc/hosts :
echo IP-DE-VOTRE-SERVEUR-IPA NOM-ET-DOMAINE-DE-VOTRE-SERVER NOM-DU-SERVER >> /etc/hosts
Ici :
echo 10.0.2.30 ipatest.testipa.local ipatest >> /etc/hosts
On vérifie à l’aide de la commande ping :
root@ipatest ~]# ping ipatest PING ipatest.testipa.local (10.0.2.30) 56(84) bytes of data. 64 bytes from ipatest.testipa.local (10.0.2.30): icmp_seq=1 ttl=64 time=0.023 ms --- ipatest.testipa.local ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.023/0.023/0.023/0.000 ms
[root@ipatest ~]# ping ipatest.testipa.local PING ipatest.testipa.local (10.0.2.30) 56(84) bytes of data. 64 bytes from ipatest.testipa.local (10.0.2.30): icmp_seq=1 ttl=64 time=0.057 ms 64 bytes from ipatest.testipa.local (10.0.2.30): icmp_seq=2 ttl=64 time=0.095 ms --- ipatest.testipa.local ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1025ms rtt min/avg/max/mdev = 0.057/0.076/0.095/0.019 ms
On lance la commande :
ipa-server-install –setup-dns
On vérifie que le nom d’hôte correspond bien à ce que l’on a indiqué plus haut :
[root@ipatest ~]# 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 FreeIPA Server. 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 DNS (bind) * Configure the KDC to enable PKINIT 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 [ipatest.testipa.local]:
On valide avec la touche [entrée]
Warning: skipping DNS resolution of host ipatest.testipa.local
The domain name has been determined based on the host name.
Please confirm the domain name [testipa.local]:
The kerberos protocol requires a Realm name to be defined.
This is typically the domain name converted to uppercase.
Please provide a realm name [TESTIPA.LOCAL]:
On choisi un mot de passe pour le Directory Manager au cas où :
Certain directory server operations require an administrative user.This user is referred to as the Directory Manager and has full accessto the Directory for system management tasks and will be added to theinstance of directory server created for IPA. The password must be at least 8 characters long. Directory Manager password:
Ne pas oubliez de le confirmer : Password (confirm):
On choisi un mot de passe administrateur (compte ‘admin’) :
The IPA server requires an administrative user, named 'admin'. This user is a regular system account used for IPA server administration.
IPA admin password:
On valide : Password (confirm):
Checking DNS domain testipa.local., please wait ... Do you want to configure DNS forwarders? [yes]: no No DNS forwarders configured Do you want to search for missing reverse zones? [yes]: The IPA Master Server will be configured with: Hostname: ipatest.testipa.local IP address(es): 10.0.2.30 Domain name: testipa.local Realm name: TESTIPA.LOCAL The CA will be configured with: Subject DN: CN=Certificate Authority,O=TESTIPA.LOCAL Subject base: O=TESTIPA.LOCAL
Chaining: self-signed BIND DNS server will be configured to serve IPA domain with: Forwarders: No forwarders Forward policy: only Reverse zone(s): No reverse zone 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. Synchronizing time Using default chrony configuration.
Warning: IPA was unable to sync time with chrony! Time synchronization is required for IPA to work correctly Configuring directory server (dirsrv). Estimated time: 30 seconds [1/44]: creating directory server instance [2/44]: enabling ldapi [3/44]: configure autobind for root [4/44]: stopping directory server [5/44]: updating configuration in dse.ldif [6/44]: starting directory server [7/44]: adding default schema [8/44]: enabling memberof plugin [9/44]: enabling winsync plugin [10/44]: configuring replication version plugin [11/44]: enabling IPA enrollment plugin [12/44]: configuring uniqueness plugin [13/44]: configuring uuid plugin [14/44]: configuring modrdn plugin [15/44]: configuring DNS plugin [16/44]: enabling entryUSN plugin [17/44]: configuring lockout plugin [18/44]: configuring topology plugin [19/44]: creating indices [20/44]: enabling referential integrity plugin [21/44]: configuring certmap.conf [22/44]: configure new location for managed entries [23/44]: configure dirsrv ccache [24/44]: enabling SASL mapping fallback [25/44]: restarting directory server [26/44]: adding sasl mappings to the directory [27/44]: adding default layout [28/44]: adding delegation layout [29/44]: creating container for managed entries [30/44]: configuring user private groups [31/44]: configuring netgroups from hostgroups [32/44]: creating default Sudo bind user [33/44]: creating default Auto Member layout [34/44]: adding range check plugin [35/44]: creating default HBAC rule allow_all [36/44]: adding entries for topology management [37/44]: initializing group membership [38/44]: adding master entry [39/44]: initializing domain level [40/44]: configuring Posix uid/gid generation [41/44]: adding replication acis [42/44]: activating sidgen plugin [43/44]: activating extdom plugin [44/44]: configuring directory to start on boot Done configuring directory server (dirsrv).
Configuring Kerberos KDC (krb5kdc) [1/10]: adding kerberos container to the directory [2/10]: configuring KDC [3/10]: initialize kerberos container [4/10]: adding default ACIs [5/10]: creating a keytab for the directory [6/10]: creating a keytab for the machine [7/10]: adding the password extension to the directory [8/10]: creating anonymous principal [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-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/28]: configuring certificate server instance
[2/28]: exporting Dogtag certificate store pin
[3/28]: stopping certificate server instance to update CS.cfg
[4/28]: backing up CS.cfg
[5/28]: disabling nonces
[6/28]: set up CRL publishing
[7/28]: enable PKIX certificate path discovery and validation
[8/28]: starting certificate server instance
[9/28]: configure certmonger for renewals
[10/28]: requesting RA certificate from CA
[11/28]: setting audit signing renewal to 2 years
[12/28]: restarting certificate server
[13/28]: publishing the CA certificate
[14/28]: adding RA agent as a trusted user
[15/28]: authorizing RA to modify profiles
[16/28]: authorizing RA to manage lightweight CAs
[17/28]: Ensure lightweight CAs container exists
[18/28]: configure certificate renewals
[19/28]: configure Server-Cert certificate renewal
[20/28]: Configure HTTP to proxy connections
[21/28]: restarting certificate server
[22/28]: updating IPA configuration
[23/28]: enabling CA instance
[24/28]: migrating certificate profiles to LDAP
[25/28]: importing IPA certificate profiles
[26/28]: adding default CA ACL
[27/28]: adding 'ipa' CA entry
[28/28]: configuring certmonger renewal for lightweight CAs
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/21]: stopping httpd
[2/21]: backing up ssl.conf
[3/21]: disabling nss.conf
[4/21]: configuring mod_ssl certificate paths
[5/21]: setting mod_ssl protocol list to TLSv1.0 - TLSv1.2
[6/21]: configuring mod_ssl log directory
[7/21]: disabling mod_ssl OCSP
[8/21]: adding URL rewriting rules
[9/21]: configuring httpd
[10/21]: setting up httpd keytab
[11/21]: configuring Gssproxy
[12/21]: setting up ssl
[13/21]: configure certmonger for renewals
[14/21]: publish CA cert
[15/21]: clean up any existing httpd ccaches
[16/21]: configuring SELinux for httpd
[17/21]: create KDC proxy config
[18/21]: enable KDC proxy
[19/21]: starting httpd
[20/21]: configuring httpd to start on boot
[21/21]: 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/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 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).
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
ipapython.dnsutil: ERROR DNS query for ipatest.testipa.local. 1 failed: All nameservers failed to answer the query ipatest.testipa.local. IN A: Server 127.0.0.1 UDP port 53 answered SERVFAIL
Configuring client side components
Using existing certificate '/etc/ipa/ca.crt'.
Client hostname: ipatest.testipa.local
Realm: TESTIPA.LOCAL
DNS Domain: testipa.local
IPA Server: ipatest.testipa.local
BaseDN: dc=testipa,dc=local
Skipping attempt to configure and synchronize time with chrony server as it has been already done on master.
New SSSD config will be created
Configured sudoers in /etc/nsswitch.conf
Configured /etc/sssd/sssd.conf
trying https://ipatest.testipa.local/ipa/json
[try 1]: Forwarding 'schema' to json server 'https://ipatest.testipa.local
/ipa/json'
trying https://ipatest.testipa.local/ipa/session/json
[try 1]: Forwarding 'ping' to json server 'https://ipatest.testipa.local/ipa/session/json'
[try 1]: Forwarding 'ca_is_enabled' to json server 'https://ipatest.testipa.local/ipa/session/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
[try 1]: Forwarding 'host_mod' to json server 'https://ipatest.testipa.local
/ipa/session/json'
SSSD enabled
Configured /etc/openldap/ldap.conf
Configured /etc/ssh/ssh_config
Configured /etc/ssh/sshd_config
Configuring testipa.local 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
Il y a eu une erreur, à savoir que le port dns n’était pas ouvert, ce qui l’a
provoqué.
Pour continuer, nous allons activer les services nécessaires dans le pare-feu (ou firewall) :
firewall-cmd --permanent --add-service=http --add-service=https --add-service=freeipa-ldap --add-service=freeipa-ldaps --add-service=kerberos --add-service=dns && firewall-cmd –reload
Voilà, vous avez un serveur simple et fonctionnel, nous allons pouvoir commencer à travailler correctement.
Vous pouvez vous connecter à distance sans avoir omis de rajouter l’ip et le nom de la machine, dans /etc/hosts comme décrit plus haut, sur votre machine locale ou autre.
https://nom.domaine.ext/ipa/ui
https://ipatest.testipa.local/ipa/ui/
Vous n’avez plus qu’a entrer le nom d’utilisateur :
admin
et son mot de passe défini plus haut.
N’oubliez pas d’initialiser le compte kerberos pour cet utilisateur si vous utilisez la ligne de commande :
kinit admin
Password for admin@TESTIPA.LOCAL: *******
A venir prochainement :
FreeIPA partie 3 : L’interface Graphique et autres…
Commandes d’administration utiles
Présentation de l’interface WEBUI et fonctionnement
Liaison avec Active directory
Commentaires récents