Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-22348

(7.4.z) Fix FIPS detection so that it also works with Java 17

    XMLWordPrintable

Details

    Description

      Within the WildFly Elytron subsystem the following method contains a utility to detect if FIPS has been enabled so we can avoid violating some FIPS requirements: -

      org.wildfly.extension.elytron.SSLDefinitions.getFipsSupplier()

      The method that is being used for this is no longer present in Java 17. Currently, we "fail safe" and just log a message if we could not detect the availability of FIPS. We need to determine how to detect FIPS for Java 17+.

      Attachments

        Issue Links

          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. WFCORE-5566 Fix FIPS detection so that it also works with Java 17

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is incorporated by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-22582 (7.4.z) Upgrade WildFly Core from 15.0.5.Final-redhat-00001 to 15.0.6.Final-redhat-00001

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          relates to

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-18717 [GSS](7.4.z) WFCORE-4296 - Illegal reflective access by org.wildfly.extension.elytron.SSLDefinitions

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Verified

          Activity

            People

              bstansbe@redhat.com Brian Stansberry
              fjuma1@redhat.com Farah Juma
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: