Jar File Signing for Forms – Addressing JRE Java Security Warnings such as “Do you want to run this application?", "Application Blocked by Java Security","Running this application may be a security risk", etc (Doc ID 2065434.1)

Last updated on AUGUST 31, 2023

Applies to:

Oracle Forms - Version 11.1.1.7.0 and later
Java SE JDK and JRE - Version 6 and later
Information in this document applies to any platform.

Purpose

Custom java code written for Forms needs to be addressed in some manner in order to meet Java Security Requirements. Failure to do so will either result in blocking of the application or Java Security Warnings which will need to be acknowledged.

Some examples are documented here.

The exact Security Warning seen will depend on the JRE version used and the particular issue found with the code.

Oracle supplied jar files such as frmall.jar, frmwebutil.jar, etc., have been signed using a Verisign certificate so there will be no Java Security Warnings or other issues with Oracle supplied jar files if one is on a current version of Forms. The purpose of this note is to discuss the various methods that can be used ensure that Java Securityr Requirements are met so that custom Java code will not be blocked or require user interaction with Java Security Warnings.

The most common Java Security issues that Forms customers need to address are related to jacob.jar, if needed for webutil ole functionality, and jar files containing icons. However, in almost all cases, any custom jar file will need to be signed appropriately.

The purpose of this document is to explain the options Forms Developers have for handling JRE/JAVA Security Warnings Related to custom java code.