After installing and configuring Oracle Forms, administrators should identify the relevant expiration dates embedded in the provided JARs in order to be prepared for their eventual expiration.
There are several signatures embedded within some of the provided JARs (for example, frmall.jar). Each signature has a unique purpose and expiration date. For information about how digital signatures work, refer to the Oracle Java documentation.
The signed JAR files can be found in the ORACLE_HOME/forms/java directory.
You can test the desired JARs using the jarsigner executable in the JDK included in the installation. For example:
The relevant expiration dates in the provided files are:
The Signer Certificate date represents the last date that the certificate can be used to sign new JAR files. Since the provided JAR was signed before that date, its expiration is mostly irrelevant and can be ignored. However, it may be used in the event the Timestamp cannot be validated, which requires an Internet connection.
The Timestamp is used to ensure that the JAR was signed during a valid period. This validation test can continue through the expiration date of the Timestamp. As mentioned, if the Timestamp cannot be validated the Signer Certificate expiration is assumed to be the last valid date the JAR can be used.
If you have JAR files that are approaching the Timestamp expiration, contact Oracle Support in order to receive updated files.
To understand more about: