184.108.40.206 Patch Released to Extend 220.127.116.11 Jar File Certificate Expiration to 1 Feb 2020
(Doc ID 2354506.1)
Last updated on MAY 29, 2018
Applies to:Oracle Forms - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
The certificate expiration date for Oracle Jar files from the terminal patch for 22.214.171.124 - patch 25645534 - is 1 Feb 2018.
Customers on 126.96.36.199 patch 25645534 and using JRE 8u151+ will see no issue because these jar files were signed with the Java Timestamp feature. What this means is that Security Warnings related to certificate expiration should not occur even after a certificate has expired since the jars were signed prior to expiration. It is important to note that the Jar files have not expired, just the certificate that was used to sign them.
However, due to some recent issues related to JRE recognition of the Timestamp feature - see <Note 2328290.1> - certain JRE versions stopped recognizing Timestamp and blocked applications whose signing certificate expired.
The issue was promptly resolved in JRE version 8u151 and above.
As a courtesy for some customers who could not upgrade their JRE to a version without the Timestamp recognition issue, Oracle has released <patch 27419810> which extends Oracle supplied jar file expiration to 1 Feb 2020.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document