Bug 509153 - java-1.6.0-openjdk-plugin does not work with Juniper VPN client
Summary: java-1.6.0-openjdk-plugin does not work with Juniper VPN client
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: java-1.6.0-openjdk
Version: 11
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Lillian Angel
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-07-01 15:09 UTC by Kedar Patankar
Modified: 2009-07-06 04:40 UTC (History)
10 users (show)

Fixed In Version: java-1.6.0-openjdk-plugin-1.6.0.0-22.b16.fc11.i586
Doc Type: Bug Fix
Doc Text:
Clone Of: 480487
Environment:
Last Closed: 2009-07-06 04:37:21 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Kedar Patankar 2009-07-01 15:09:57 UTC
My company has a Juniper netscreen VPN box. It works perfectly with SUN JRE on Fedora-10 and below. It does not work with the OpenJDK that comes with Fedora-11 or any of its updates. I get a dialog box asking about running the appet/trusting the publisher. I answer "yes always trust" for all the dialogs. It starts the applet, but then quits saying "Config failed".

I tried F11 with openjdk 22.b16 update. No luck.

I would be glad to provide any debugging data.

Comment 1 Kedar Patankar 2009-07-06 04:37:21 UTC
Everything works.
Just tested again with latest updates on i386 platform. Following are the component versions on my working setup:

java-1.6.0-openjdk-plugin-1.6.0.0-22.b16.fc11.i586
firefox-3.5-1.fc11.i586

Thanks a *LOT*.
I have never before seen OpenJDK/Icedtea plugin work with Juniper SSL/VPN. Now I need to test this in x86-64 mode.

For now, you can close this bug.

Comment 2 Kedar Patankar 2009-07-06 04:40:39 UTC
The original bug was filed with plain vanilla F11 setup with firefox 3.5 beta. The latest updates for openjdk and firefox (and what else, there was too much stuff to keep track of) seem to make it work like a charm.


Note You need to log in before you can comment on or make changes to this bug.