Cryptoj.jar file in Prior 12.8 version SDK kit uses an expired signing cert.
Customer reports that WebSphere application 9.0.5 server prevents cryptoj.jar from loading because the cert used to sign the jar file is expired.
Looking at the cert info printed by jarsigner:
X.509, CN="RSA, The Security Devision of EMC", OU=Java Software Code Signing, O=Sun Microsystems Inc
[certificate expired on 2/3/17 1:50 PM]
X.509, CN=JCE Code Signing CA, OU=Java Software Code Signing, O=Sun Microsystems Inc, L=Palo Alto, ST=CA, C=US
[certificate expired on 4/25/20 3:00 AM]
SDK Release version : Any 12.51 to 12.7
Component : SITEMINDER -SDK
12.8 SDK does not have cryptoj.jar.
After Upgrading to CA SSO 12.8, any custom code that uses cryptoj.jar may be no longer working. Hence, custom code needs to be rebuilt with 12.8 SDK where old cryptoj.jar is no longer referenced.