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.

This bug was initially created as a copy of Bug #2094027

I am copying this bug because: 

FIPS support in RHEL 9 needs to be kept in sync with RHEL 8.

The module jdk.crypto.ec is not granted permission to access the package jdk.internal.access in java.base (java.lang.RuntimePermission "accessClassInPackage.jdk.internal.access"). Under the presence of a Security Manager, any such access throws a security exception. The reason why jdk.crypto.ec needs access is legitimate: determining if OpenJDK is configured in FIPS mode. A similar bug involving the module jdk.crypto.cryptoki has been fixed before [1].

The patch to fix this issue has been authored by @Severin Gehwolf and successfully tested after inclusion in portable builds of java-17-openjdk [2].

--
[1] - https://bugzilla.redhat.com/show_bug.cgi?id=1996182
[2] - http://pkgs.devel.redhat.com/cgit/rpms/java-17-openjdk/commit/java-17-openjdk.spec?h=openjdk-portable-rhel-7&id=d8ffcb9d1ae06c139786858b114bd19c9359220e

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 (java-17-openjdk bug fix and enhancement update), 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:6709