SOI 4.2 Cum 2 - Signer certificates of jar files expired
search cancel

SOI 4.2 Cum 2 - Signer certificates of jar files expired


Article ID: 231834


Updated On:


CA Service Operations Insight (SOI)


Post upgrade to CA Service Operations Insight 4.2 Cum 2, the SOI console fails to start. It is blocked by the Java security check which complains about expired certificates with the warning below:
This jar contains entries whose signer certificate has expired.
This jar contains signatures that do not include a timestamp. Without a timestamp, users may not be able to validate this jar after any of the signer certificates expire (as early as 2022-01-08).



Release : 4.2

Component : Service Operations Insight (SOI) Manager

This problem affects all SOI installations with the latest release CUM 2 (


Problem caused by  jarsigner, signer certificate expired and needs new jars with updated signer certificates.
The actual certificate is valid until 2024 but the jar signer certificate has expired.


This issue will be fixed in the next monthly patch and upcoming cumulative patches if any.

In the mean time, Please apply the attached updated jars with updated signer certificates. 

Steps to apply the jars:

1. Stop "CA SOI User Interface Server" service
2. Take the backup of existing JARs at <SOI_HOME>\SamUI\webapps\sam\lib.
3. Replace with the downloaded JARs from the case
4. Start "CA SOI User Interface Server" service

Attachments get_app