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:6691