RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Working of FIPS mode in OpenSSL 3.0 deviates from the upstream FIPS behaviour.
Working of FIPS in upstream is described here:
https://github.com/openssl/openssl/blob/master/README-FIPS.md

RHEL-9

When is FIPS provider loaded by default?

1. If the kernel FIPS flag is set, then OpenSSL will automatically load the FIPS provider.
This means that no additional configuration is required to be set manually by the user.
No changes in openssl.cnf.
HMAC calculations will be done on fip.so.

2. If the kernel FIPS flag is not set, then OpenSSL will automatically load the DEFAULT provider.
(no config changes required as mentioned before)
However, if the user, wants to add other sections and load different providers through configuration
via openssl.cnf, this is fully permitted. It should be noted that this configuration will then take effect
and override what was configured by default. It is generally not recommended to customize openssl.cnf,unless it is absolutely necessary.

*** Bug 1985363 has been marked as a duplicate of this bug. ***

ossl_provider_add_conf_module seems a relevant place to load the FIPS provider implicitly for the end user.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (new packages: openssl), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2022:3900