Skip to main content
1-Visitor
April 5, 2010
Question

Java 1.6 Update 19 "Warning - Security" dialog disables 9.1 applets or triggers errors

  • April 5, 2010
  • 12 replies
  • 3824 views
The Java 1.6 Update 19 released on April 1st has a new security Warning
that is being triggered by Windchill applets in 9.1. The default of
"Yes" prevents the applets from working correctly.

We haven't finished tested yet, but clicking "No" on the dialog seems to
be a "one time only per applet" workaround. ("Just Say No") There is
also a java client setting to reduce the overall security level (see
link below).

The "Warning - Security" dialog says:
"Java has discovered application components that could indicate a
concern."
"The applet contains both signed and unsigned code."
"Block potentially unsafe components from being run? (recommended)"

It wasn't obvious to users that "Yes" means "Don't run the application"
and "No" means "Run the application (with some restrictions)".

One reported error that happens if you click "Yes" was a dialog from IE
8 titled "Message from Webpage" that said: "ATTENTION: An error occured
while uploading the file. Please contact your administrator. Error:
[object Error]"

We've seen two file attachment applets on the warning dialog:
fileSelectionAndUploadAppletApplet, and
dragAndDropFileSelectionAppletApplet when creating documents and
updating Change Notice attachments.

I have an SPR 1969357 for the issue with a severity of high and tech
support told me it will be fixed in 9.1 m060.

Here is a great, um.. "Oracle", Java page "Mixing Signed and Unsigned
Code" that describes the dialog and options for users and developers.

12 replies

12-Amethyst
May 31, 2010
That's an interim approach.

Another is to disable the security warning in the plug-in settings as
per
12-Amethyst
May 31, 2010
I should also note that disabling the security warning will not address
the other big issue that Java 6 Update 19 poses -- it breaks all
drag-and-drop in applets. Resolving this requires a code change (or
editing one's java.policy file).