2471281 - Jurisdiction policy files are not signed by trusted signers! SUM issue on START-SYSTEM-DUAL-STACK or RESTART-SYSTEM

Software Update Manager (SUM) throws the below error in the step: START-SYSTEM-DUAL-STACK or RESTART-SYSTEM-JAVAONLY
(Log file: <Path to SUM>/SUM/sdt/log/SUM/START-SYSTEM-DUAL-STACK_XX.LOG or <Path to SUM>/SUM/sdt/log/SUM/RESTART-SYSTEM-JAVAONLY_XX.LOG)

<TIMESTAMP> [Info ]: Command line: /usr/sap/<SID>/instance<XX>/exe/sapcontrol -nr <XX> -host <hostname> -user <sidadm> <SecureField> -prot NI_HTTP -function WaitforStarted 144000 5
<TIMESTAMP> [Info ]: Standard out: <Path to SUM>/SUM/sdt/log/SUM/SAPCONTROL_WAITFORSTARTED_XX_YY.OUT
<TIMESTAMP> [Info ]: Process ID 34 has been started.
<TIMESTAMP> [Info ]: Waiting for process ID 34, name sapcontrol to finish.
<TIMESTAMP> [Info ]: Process ID 34, name sapcontrol has been finished, exit code 2.
<TIMESTAMP> [Error ]: Return code condition success evaluated to false for process sapcontrol for action wait for started.

<TIMESTAMP> [Error ]: The following problem has occurred during step execution: com.sap.sdt.util.diag.DiagException: Could not check status of SAP instance with number <XX>.
Could not check if the instance number <XX> on host <hostname> is started.
Sapcontrol client could not perform action wait for started on instance <XX>
Return code condition success evaluated to false for process sapcontrol for action wait for started.

The WaitForStarted Webmethod times out with exit code 2 (Log file: <Path to SUM>/SUM/sdt/log/SUM/SAPCONTROL_WAITFORSTARTED_XX_YY.OUT)

<TIMESTAMP>
WaitforStarted
FAIL: Timeout

The reason for timeout can be seen in the dev_jstart (Log file location: /usr/sap/<SID>/instance<XX>/work/)

F ********************************************************************************
F *** ERROR => Node 'bootstrap' failed with exit code 500.
F ***
F *** Please see section 'Failures in the 'synchronizing binaries' phase'
F *** in SAP Note 1316652 for additional information and trouble shooting advice.
F ********************************************************************************
F
F [Thr 01] *** LOG => exiting (exitcode 22002, retcode 1).

The actual error for the failure in bootstrap can be seen in the jvm_bootstrap.out and the log_bootstrap.X.log files in the work directory (Log file location: /usr/sap/<SID>/instance<XX>/work)

Starting to initialize database connection
Exception occurred for component [internal/unkown] of type [unkown]
java.lang.ExceptionInInitializerError
.
.

at java.lang.reflect.Method.invoke(Method.java:597)
at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:162)
Caused by: java.lang.SecurityException: Cannot set up certs for trusted CAs
at javax.crypto.JceSecurity.<clinit>(JceSecurity.java:266)
... 20 more
Caused by: java.lang.SecurityException: Jurisdiction policy files are not signed by trusted signers!
at javax.crypto.JceSecurity.loadPolicies(JceSecurity.java:545)
.
.
[Bootstrap]> Error during synchronization. More details: the previous log entries

• SAP NetWeaver Application Server for Java
• SUM

START-SYSTEM-DUAL-STACK, RESTART-SYSTEM-JAVAONLY, WaitForStarted, "Time out", JCE, unlimited, jvm_bootstrap,log_bootstrap, com.sap.sdt.util.diag.DiagException, java.lang.ExceptionInInitializerError, java.lang.SecurityException, "Cannot set up certs for trusted CAs", "Jurisdiction policy files are not signed by trusted signers!", bootstrap, ERROR => Node 'bootstrap' failed with exit code 500,Could not check status of SAP instance with number , KBA , kde , BC-JVM , SAP Java Virtual Machine , BC-JAS-COR , Enterprise Runtime, Core J2EE Framework , BC-UPG-TLS-TLJ , Upgrade tools for Java , Problem