Jar File Expiration for Forms 188.8.131.52 and Higher on 6 July 2013
(Doc ID 1550175.1)
Last updated on MAY 08, 2020
Oracle Forms - Version 184.108.40.206.0 and later Information in this document applies to any platform.
The trusted certificate used to sign Oracle provided jar files such as frmall.jar, frmwebutil.jar, etc. will expire on July 6, 2013. In previous versions of Forms, such as early versions of Forms 10gR2, Java Warning messages would occur after the expiration date. For examples of what would be seen, please review <Note 760645.1> and <Note 1307787.1>.
Beginning with Forms 220.127.116.11, Forms development began using the Signature Time Stamp Support feature of Java to prevent a warning if the jar file was signed by a valid certificate at the time of its creation prior to the certificate's expiration date. The passage of this date does not cause a change in behavior or security reliability. This date merely means that the jar file had to be signed before that date.
With the use of the Signature Time Stamp method, there is no impact on end users or change in application functionality. The expiration date will pass and no expiration warning will display.
The purpose of this FAQ is to provide details on what will happen after this date and what Oracle Forms users should know related to this.
Questions and Answers
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!