My Oracle Support Banner

Siebel Management Console (SMC) Is Not Accessible Due to Authentication Failure After Applying 23.3 Monthly Update On AIX OS Platform - java.lang.SecurityException: Jurisdiction policy files are not signed by trusted signers! (Doc ID 2987142.1)

Last updated on MARCH 06, 2024

Applies to:

Siebel CRM - Version 23.3 to 23.10 [Release V17]
Information in this document applies to any platform.

Symptoms

After applying 23.3 on top of 21.12 installation the Siebel Management Console (SMC) is not accessible due to authentication failure, and the following error is observed on the UI:

The user ID or password that you entered is incorrect

The Application URL is not reachable as the following error is observed on the UI:

Application Interface is in Lightweight Mode. Deploy profile to proceed.

Both the Application Containers (external and internal) fail to initialize the HTTPS listener connector as the following error is observed in the catalina.YYYY-MM-DD.log located under the applicationcontainer_*/logs directory:

13-Nov-2023 10:24:34.232 SEVERE [main] org.apache.catalina.util.LifecycleBase.handleSubClassException Failed to initialize component [Connector[HTTP/1.1-https_listen_port_number]]
java.lang.ExceptionInInitializerError
  at java.lang.J9VMInternals.ensureError(J9VMInternals.java:157)
  at java.lang.J9VMInternals.recordInitializationFailure(J9VMInternals.java:146)
  at javax.crypto.Cipher.getInstance(Unknown Source)
  at com.ibm.jsse2.al.b(al.java:169)
  at com.ibm.jsse2.n.a(n.java:41)
  at com.ibm.jsse2.n.(n.java:107)
  at com.ibm.jsse2.n.(n.java:221)
  at com.ibm.jsse2.n$e.a(n$e.java:5)
  at com.ibm.jsse2.ak.(ak.java:43)
  at com.ibm.jsse2.bj.(bj.java:378)
  at com.ibm.jsse2.SSLSocketFactoryImpl.createSocket(SSLSocketFactoryImpl.java:12)
  at javax.net.ssl.SSLContextSpi.a(SSLContextSpi.java:2)
  at javax.net.ssl.SSLContextSpi.engineGetSupportedSSLParameters(SSLContextSpi.java:7)
  at javax.net.ssl.SSLContext.getSupportedSSLParameters(SSLContext.java:45)
  at org.apache.tomcat.util.net.jsse.JSSESSLContext.getSupportedSSLParameters(Unknown Source)
  at org.apache.tomcat.util.net.jsse.JSSEUtil.initialise(Unknown Source)
  at org.apache.tomcat.util.net.jsse.JSSEUtil.getImplementedProtocols(Unknown Source)
  at org.apache.tomcat.util.net.SSLUtilBase.(Unknown Source)
  at org.apache.tomcat.util.net.jsse.JSSEUtil.(Unknown Source)
  at org.apache.tomcat.util.net.jsse.JSSEUtil.(Unknown Source)
  at org.apache.tomcat.util.net.jsse.JSSEImplementation.getSSLUtil(Unknown Source)
  at org.apache.tomcat.util.net.AbstractJsseEndpoint.createSSLContext(Unknown Source)
  at org.apache.tomcat.util.net.AbstractJsseEndpoint.initialiseSsl(Unknown Source)
  at org.apache.tomcat.util.net.NioEndpoint.bind(Unknown Source)
  at org.apache.tomcat.util.net.AbstractEndpoint.bindWithCleanup(Unknown Source)
  at org.apache.tomcat.util.net.AbstractEndpoint.init(Unknown Source)
  at org.apache.coyote.AbstractProtocol.init(Unknown Source)
  at org.apache.coyote.http11.AbstractHttp11Protocol.init(Unknown Source)
  at org.apache.catalina.connector.Connector.initInternal(Unknown Source)
  at org.apache.catalina.util.LifecycleBase.init(Unknown Source)
  at org.apache.catalina.core.StandardService.initInternal(Unknown Source)
  at org.apache.catalina.util.LifecycleBase.init(Unknown Source)
  at org.apache.catalina.core.StandardServer.initInternal(Unknown Source)
  at org.apache.catalina.util.LifecycleBase.init(Unknown Source)
  at org.apache.catalina.startup.Catalina.load(Unknown Source)
  at org.apache.catalina.startup.Catalina.load(Unknown Source)
  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:90)
  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
  at java.lang.reflect.Method.invoke(Method.java:508)
  at org.apache.catalina.startup.Bootstrap.load(Unknown Source)
  at org.apache.catalina.startup.Bootstrap.main(Unknown Source)
Caused by: java.lang.SecurityException: Cannot set up certs for trusted CAs
  at javax.crypto.b.(Unknown Source)
  ... 40 more
Caused by: java.lang.SecurityException: Jurisdiction policy files are not signed by trusted signers!
  at javax.crypto.b.a(Unknown Source)
  at javax.crypto.b.c(Unknown Source)
  at javax.crypto.b.access$600(Unknown Source)
  at javax.crypto.b$a.run(Unknown Source)
  at java.security.AccessController.doPrivileged(AccessController.java:747)
  ... 41 more

STEPS

The issue can be reproduced at will with the following steps:
1. Install 23.3 Monthly Update on top of 21.12 installation
2. Try to start the application containers (external or internal)
3. The above mentioned symptoms are observed

Changes

Siebel 23.3 Monthly Update installation on top of an existing installation 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.