786786 - Enabling Java applet

Status: RESOLVED INCOMPLETE

(Plugins Graveyard :: Java (Oracle), defect)

Description

[Marc Meltzer]

Is there something in FF10 that blocks Java applets from running?  I have an applet that ran in 3.6 but does not in 10.0.6.  Maybe it’s because the applet is unsigned.  Here is what happens:
 
1.       User goes to webpage that calls for Java applet to load.
2.       Dialog box pops up asking if you want to allow the applet to run
3.       Proceed with task
 
In Firefox 3.6, the applet runs fine, but in 10.0.6, the applet does not behave properly.  The applet is related to our PKI, so I don't have too many details at the moment.
 
Is there a particular setting I should configure to allow the unsigned applet to run?
 
I’ve been reading some stuff on Oracle’s web site, but the problem is not with Java per se, because I have not changed Java.

If I uninstall 10 and install 3.6, the applet runs fine.

Comment 1

[Marc Meltzer]

I believe we are using Java 6 update 33.

Comment 2

[Lukas Blakk [:lsblakk] use ?needinfo]

CC-ing addons/plugins folks as well as requesting QA to see if we can verify there is a regression here -- can someone confirm if this worked in earlier versions of esr or even in FF10 and FF15?

Marc, if you can provide a link to the applet or something for QA to test against, that would help.

Comment 3

[Marc Meltzer]

The specific applet is for a PKI system used by the Registration Authorities.  The problem is it is on a classified network, so I don't know if I can provide you anything to test with.  I have to see who the vendor is and maybe we can work around the classification issue.

I am also going to try multiple past versions of FF and unlocked current version to see if I can isolate anything.

Comment 4

[Benjamin Smedberg]

Are you sure that's the version of Java you're using? We blocked Java version 6 update 30 and below: https://blog.mozilla.org/addons/2012/04/02/blocking-java/

Please include information from about:plugins about the exact version of Java being used.

Do other sites that use Java work? e.g. http://www.java.com/en/download/testjava.jsp

Comment 5

[Marc Meltzer]

I confirmed with my customer it is update 33, but again, it's not Java that is the problem, because the applet works with FF 3.6.
I also can't test Java on this system, because it's a closed network, but again, the applet does work with FF 3.6 installed.

I did try FF 4.0.1 and the applet did not work, so it looks like the problem goes all the way back.  FF 15 also does not work.

Here is more detail:
The applet is Unitrends WebRAO.  It is for registering users into the PKI system.  When the initial page pops up, I am prompted to unblock the applet as the certificate has expired (but that shouldn't be a problem, right, because it works in 3.6?).  Besides that, the applet is of mixed signatures (some code signed, some unsigned).
The user logs in and goes to register a person.  After the information is entered, the user clicks on submit and the system is supposed to start generating a key pair, then prompt to create a password.

In the newer versions, instead of generating the keys, the system pops up a dialog that says something like no key policies are set.

(And can someone get the Product and Component fields to stick, so I don't have to set them every time I submit a comment?)
So Firefox is preventing something from getting to Java.

Comment 6

[Alex Keybl [:akeybl]]

Let us know as soon as you have a test case that we can reproduce with. Thanks!

Comment 7

[Marc Meltzer]

I'm not exactly sure how I'm going to provide you a test case.

As mentioned, the particular applet is part of a PKI registration portal.  I expect you'd need the backend to be able to truly reproduce, as you need to login to the system first, then you need to attempt to register a user before the error even occurs.

I'm trying to find out versions or vendors, but that is proving difficult so far.  I'll keep trying.

Comment 8

[u279076]

Any progress on this Marc? Is it still an issue with the latest Firefox ESR?

Comment 9

[Alice0775 White]

FYI, It works if set security.fileuri.strict_origin_policy = false
Not recommended!

Comment 10

[Benjamin Smedberg]

Closing old bugs in the Plugins component. We aren't going to track issues in 3rd-party plugins in the Mozilla bug tracker. In addition, support for NPAPI plugins will be removed at the end of this year; for more details see the post at https://blog.mozilla.org/futurereleases/2015/10/08/npapi-plugins-in-firefox/

If there is a serious bug in Firefox, it needs to be filed in the "Core" product, "Plug-Ins" component.