For Wildfly deployments: After patching RSA Identity Governance & Lifecycle 7.2.1 to P12 (or later) or 7.5.0 to P07 (or later), the server fails to start. The following errors are logged to aveksaServer.log file:
java.security.NoSuchProviderException: JCE cannot authenticate the provider JsafeJCE at javax.crypto.b.a(Unknown Source) at javax.crypto.SecretKeyFactory.getInstance(Unknown Source) at com.aveksa.common.crypto.CryptoJBasedStringEncryptor.buildKey(CryptoJBasedStringEncryptor.java:404)
For IBM WebSphere deployments: After patching RSA Identity Governance & Lifecycle 7.2.1 to P12 (or later) or 7.5.0 to P07 (or later), or upgrading to SecurID Governance & Lifecycle 7.5.2 P03, the server fails to start. The following ERROR level log message are logged to the systemout.log file:
06/16/2022 09:38:01.767 ERROR (server.startup : 1) [com.aveksa.migration.jdbctool.CheckDatabase] Error reading Aveksa_System.cfg java.lang.IllegalStateException: An issue with handling encryption was encountered
16/2022 09:39:03.764 ERROR (server.startup : 1) [com.aveksa.server.runtime.AveksaSystem] Unable to check Database. java.lang.NullPointerException
For Wildfly deployments, ensure you have applied the latest JAVA update upgradeJDK8u312b07.tar (or later) available with the above mentioned versions/patches.
For WebLogic deployments, ensure you update your JAVA to the latest version.
For IBM WebSphere deployments, IBM WebSphere must be updated to the the most recent version in order to support the current RSA Governance & Lifecycle patches. The following are the minimum requirements:
See additional information in the following knowledgebase article for a similar failure when attempting to run an older RSA Governance & Lifecycle version with a later IBM fixpack:
KB 000044471 - “An issue with handling encryption was encountered" with IBM JDK 1.8.0_281 and later in RSA Identity Governance & Lifecycle