Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-66180

BouncyCastle plugin should not collide with BC-FIPS if JVM has BouncyCastle FIPS jars

XMLWordPrintable

    • ouncycastle-api:2.22

      IF the JVM running Jenkins has been configured for FIPS compliance by using the Bouncy Castle FIPS provider (https://www.bouncycastle.org/fips-java/) the plugin currently fails to start due to classname collisions and this causes plugins that depend on it to also fail.

      The FIPS jars are somewhat (but not 100%) compatable with the regular BouncyCastle Jars and many (but not all) plugins will work happily in the presence of either of these (with the [exception of SAML )

      https://groups.google.com/g/pac4j-dev/c/jDeEN-mUwd0]Therefore the plugin should tollerate becoming a no-op plugin if it detects BouncyCastle FIPS is configured in the controller JVM.

      If the controller JVM has been configured with FIPS it is reasonable to assume all agents must also be configured in the same way,

            teilo James Nord
            teilo James Nord
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: