What causes Crypto-J is disabled, a FIPS 140 required self-integrity check failed in JBoss EAP?

Solution Verified - Updated -

Issue

  • Starting a deployment, this exception is thrown

    java.lang.SecurityException: Crypto-J is disabled, a FIPS 140 required self-integrity check failed
            at com.rsa.jsafe.CryptoJ.a(Unknown Source)
            at com.rsa.jsafe.CryptoJ.f(Unknown Source)
            at com.rsa.jsafe.JSAFE_SecureRandom.a(Unknown Source)
            at com.rsa.jsafe.JSAFE_SecureRandom.getInstance(Unknown Source)
    
    java.lang.SecurityException: JsafeJCE provider self-integrity check failed com.rsa.jsafe.provider.JsafeJCE.<init>(Unknown Source)
    Caused by: java.lang.SecurityException: JCE cannot authenticate the provider IngrianProvider
            at javax.crypto.Cipher.getInstance(DashoA13*..) [na:1.6]
            at javax.crypto.Cipher.getInstance(DashoA13*..) [na:1.6]
            ...
    Caused by: java.util.jar.JarException: Cannot parse jar:file:/path/to/jboss-as/server/profile/deploy/myapplication.ear!/ingrian-nae.jar
            at javax.crypto.SunJCE_c.a(DashoA13*..) [na:1.6]
            at javax.crypto.SunJCE_b.b(DashoA13*..) [na:1.6]
            at javax.crypto.SunJCE_b.a(DashoA13*..) [na:1.6]
            ... 296 common frames omitted
    

Environment

  • JBoss Enterprise Application Platform (EAP)
    • 5
    • 6
    • 7
  • RSA CryptoJ deployed in a WAR or EAR

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content