We resolved the issue yesterday using an unusual workaround. The problem stemmed from the presence of the PD.jar
file in both WAS_HOME/tivoli/tam/
and WAS_HOME/java/8.0/jre/lib/ext/
. In our setup, we had deployed the latest version of PD.jar
(10.0.7.0), which introduced class conflicts that interfered with certificate operations in WAS. Replacing it with an older version (9.0.2.0) resolved the issue, allowing certificate operations to function correctly.
We confirmed that reverting to the older PD.jar
did not impact our TAI++ SSO functionality. Moving forward, it would be ideal for the WAS and ISAM teams to coordinate and address compatibility issues introduced by newer versions of the PD.jar
file.
------------------------------
Ninad Tamras
------------------------------
Original Message:
Sent: Mon April 28, 2025 09:03 AM
From: Brian S Paskin
Subject: WAS Default Self-signed certificate renewal is failing
You did the correct thing and opened a PMR.
------------------------------
Brian S Paskin
Sr. Technology Engineer
IBM Cloud Engineering
Original Message:
Sent: Mon April 28, 2025 08:46 AM
From: Ninad Tamras
Subject: WAS Default Self-signed certificate renewal is failing
But how do we resolve this issue? We are already at WAS 9.0.5.21 level.
------------------------------
Ninad Tamras
Original Message:
Sent: Mon April 28, 2025 05:36 AM
From: Brian S Paskin
Subject: WAS Default Self-signed certificate renewal is failing
This error occurred in 855 and was fixed several years ago also with a fix for 905. So it might be a regression.
------------------------------
Brian S Paskin
Sr. Technology Engineer
IBM Cloud Engineering
Original Message:
Sent: Mon April 28, 2025 03:11 AM
From: Ninad Tamras
Subject: WAS Default Self-signed certificate renewal is failing
Hello Gabriel,
We have raised PMR TS019146801 and attached the logs and other screenshots. Would highly appreciate if you could take a look. I am not sure how to share the logs with you here. The only exception we see every time we try renew certificate, has been shared above in RED color.
------------------------------
Ninad Tamras
Original Message:
Sent: Mon April 28, 2025 02:31 AM
From: Gabriel Aberasturi
Subject: WAS Default Self-signed certificate renewal is failing
Hello Ninad,
I suggeset to enable security traces and try again to get more details about the fail. If you can share here
Procedure
1. Open the WebSphere® Application Service Integrated Solutions Console.
2. Expand Troubleshooting and select Logs and trace.
3. Select the server on which you want to enable traces, and then select Diagnostic Trace.
4. Click the Runtime tab.
5. lick Change Log Detail Levels.
6. Set a trace level, select Save runtime changes to configuration as well, and click Apply.
com.ibm.ws.security.*=all=enabled
Tell us if you need more support
------------------------------
Gabriel Aberasturi
Middleware Architect
Versia Sistemas TI
Original Message:
Sent: Fri April 25, 2025 03:21 AM
From: Ninad Tamras
Subject: WAS Default Self-signed certificate renewal is failing
Hi All,
We are using WAS 9.0.5.21 and the auto-renewal of the WAS certificates did not seem to happen as expected, thus causing the certificates to expire. Now, I am trying the renew the certificate manually from the WAS Admin Console but it is failing with below error :
An error occurred renewing default: com.ibm.security.certclient.base.PkRejectionException: 3008-737 A certificate attribute was not recognised. (wraps: java.security.cert.CertificateException: Subject class type invalid.)
Any pointers on fixing this issue?
------------------------------
Ninad Tamras
------------------------------