Description of problem: The RHEL 9 client configured for FIPS fails to join an IPA realm if the IPA server was created in FIPS. The RHEL 9 client NOT configured for FIPS will successfully join an IPA realm if the IPA server was created in FIPS. The RHEL 9 client configured for FIPS will successfully an IPA realm of the IPA server was not created it FIPS. Version-Release number of selected component (if applicable): ipa-client-4.9.8-7.el9_0.x86_64 How reproducible: To replicate the problem, follow the following instructions. I have replicated this issue many times. We have hundreds of nodes set with FIPS enabled. Only the RHEL 9.0 systems will not join the IPA realm. 1. Create a RHEL 9.0 system 2. Enable FIPS: fips-mode-setup --enable 3. Reboot 4. login 5. ipa-client-setup -N (enter username, password, etc.) 6. The node fails to join the IPA realm 7. Disable FIPS: fips-mode-setup --disable 6. Reboot 7. Login 8. ipa-client-setup -N (enter username, password, etc.) 9. Node joins the IPA realm with no error. Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Hi @abroy I was not able to reproduce the issue. I configured a RHEL 9 server in FIPS mode, then ran ipa-server-install, then configured a client machine in FIPS mode, and ran ipa-client-install. Both machines were installed with RHEL 9 and ipa 4.9.8-7.el9_0. The client installation succeeds with admin or a user member of the admins group. Can you provide the server sos report as well as the client sos report, or link to a customer case?
In the linked case, the customer has a RHEL 8.6 server, and that is a completely different setup. This should have been mentioned in the BZ description. With this specific config, the issue can be reproduced: 1. install a 8.6 server in FIPS mode 2. install a 9.0 client in FIPS mode The installation fails when the client tries to obtain a kerberos TGT with the principal provided to ipa-client-install --principal XXX: In krb5kdc.log on the master: Jul 07 04:58:20 master.testrelm.test krb5kdc[6251](info): AS_REQ (2 etypes {aes256-cts-hmac-sha384-192(20), aes128-cts-hmac-sha256-128(19)}) 10.0.192.183: BAD_ENCRYPTION_TYPE: admin for krbtgt/TESTRELM.TEST, KDC has no support for encryption type On the master: [root@master ~]# cat /etc/krb5.conf.d/crypto-policies [libdefaults] permitted_enctypes = aes256-cts-hmac-sha1-96 aes256-cts-hmac-sha384-192 aes128-cts-hmac-sha1-96 aes128-cts-hmac-sha256-128 On the client: # cat /etc/krb5.conf.d/crypto-policies [libdefaults] permitted_enctypes = aes256-cts-hmac-sha384-192 aes128-cts-hmac-sha256-128 Moving the issue to krb5 component for further analysis.
A FIPS-enabled RHEL9 client will fail to authenticate against any RHEL8 IPA server (FIPS or non-FIPS) because none of the encryption types supported by IPA on RHEL8 are allowed on RHEL9 in FIPS mode, which aims to comply with FIPS 140-3, a newer and more strict version of the standard (more information in bug 2039684). Fixing this issue is not trivial, because it requires to update user passwords and to add new keys to all services and import these new keys to service keytabs. We are planning to provide batch script to automate this process as much as possible.
The encrypt type aes256-cts-hmac-sha1-96 was used. It is the default for RHEL 8 because: 1. HMAC-SHA1 is approved in CMVP 2. AES SHA-1 HMAC encryption types remain essential for interoperability with Active Directory because they are the "best" ones MIT Kerberos has in common with AD [2]. However, FIPS mode in RHEL 9 does not contain HMAC-SHA1-96 ~~~ mac = AEAD HMAC-SHA2-256 HMAC-SHA2-384 HMAC-SHA2-512 group = SECP256R1 SECP384R1 SECP521R1 \ FFDHE-2048 FFDHE-3072 FFDHE-4096 FFDHE-6144 FFDHE-8192 ~~~ Also Bug 2006843 - Disable SHA-1 in FIPS policy That's why it failed. The workaround will be using FIPS:AD-SUPPORT because ~~~ ... # This subpolicy is provided for enabling aes256-cts-hmac-sha1-96, # the strongest Kerberos encryption type interoperable with Active Directory. cipher@kerberos = AES-256-CBC+ mac@kerberos = HMAC-SHA1+ ~~~ 1. https://csrc.nist.gov/publications/detail/sp/800-140c/rev-1/final 2. https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-kile/b3fa11e2-a878-4734-a9e2-2d77a5a06108