Last updated on JUNE 30, 2017
Applies to:Oracle Fusion Applications Common Components - Version 22.214.171.124.0 and later
Oracle Fusion Application Toolkit - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
Oracle Fusion Applications Release note(Doc ID 1355561.1), states how to fix this original BAD_CERTIFICATE error points you to fixing the certificate in fusion_trust.jks in the $WL_HOME/server/lib directory.
When I do see ( As an e.g.):
keytool -list -v -keystore $WL_HOME/server/lib/fusion_trust.jks
Stated that offending certificate (now fixed) and see all the other certificates in this file along with their expire date, can see one coming up in August:
Alias name: xxxxxxxxxxx
Creation date: Oct 12, 2012
Entry type: trustedCertEntry
Owner: CN=GTE CyberTrust Root 5, OU="GTE CyberTrust Solutions, Inc.", O=GTE Corp
Issuer: CN=GTE CyberTrust Root 5, OU="GTE CyberTrust Solutions, Inc.", O=GTE Cor
Serial number: 1b6
Valid from: Fri Aug 14 07:50:00 PDT 1998 until: Wed Aug 14 16:59:00 PDT 2013
Signature algorithm name: SHA1withRSA
You can see the valid from dates above that shows this certificate will expire on Wed Aug 14 16:59:00 PDT 2013.
You do not want to get BAD_CERTIFICATE error before fixing it, and instructions to recreate/renew this certificate listed below.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms