Identity Manager server does not start after JBoss and JDK upgrade with error java.lang.SecurityException: Can not initialize cryptographic mechanism

Products

• CA Identity Manager

Issue/Introduction

A customer upgraded JBoss from v6.2 to v7.2, and also upgraded Oracle JDK.

After that IM server does not start, and the following error is reported in server.log:

02:32:12,127 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service org.wildfly.core.management.security.realm.ApplicationRealm.ssl-context: org.jboss.msc.service.StartException in service org.wildfly.core.management.security.realm.ApplicationRealm.ssl-context: Failed to start service
 at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1730) [jboss-msc-1.4.5.Final-redhat-00001.jar:1.4.5.Final-redhat-00001]
.....
Caused by: java.lang.ExceptionInInitializerError
 at javax.crypto.Cipher.getInstance(Cipher.java:518) [jce.jar:1.8.0_271]
.....
Caused by: java.lang.SecurityException: Can not initialize cryptographic mechanism
 at javax.crypto.JceSecurity.<clinit>(JceSecurity.java:93) [jce.jar:1.8.0_271]
 ... 25 more
Caused by: java.lang.SecurityException: The jurisdiction policy files are not signed by the expected signer! (Policy files are specific per major JDK release.Ensure the correct version is installed.)
 at javax.crypto.JarVerifier.verifyPolicySigned(JarVerifier.java:336) [jce.jar:1.8.0_271]
.....

Environment

Release : 14.x

Component : Identity Manager

Cause

Java security policy files are misplaced, or security policy version is wrong.

Resolution

Download Java security policy that corresponds to the JDK version in use, and install it, then restart JBoss.

Installation steps described by Oracle: https://docs.oracle.com/cd/E84221_01/doc.8102/E84237/index.htm?toc.htm?212338.htm