Bug 835665 - Unable to launch Juniper VPN on Fedora 17
Summary: Unable to launch Juniper VPN on Fedora 17
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: java-1.7.0-openjdk
Version: 17
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Deepak Bhole
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-06-26 18:48 UTC by johnav
Modified: 2012-06-27 08:25 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
- Fedora 17 64 bit - Firefox 12 - IcedTeaPlugin1.2 - Java 1.7.0_b147-icedtea
Last Closed: 2012-06-27 08:25:28 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
icedtea debug logs (17.18 KB, application/octet-stream)
2012-06-26 18:48 UTC, johnav 		no flags Details
java console logs (1.52 KB, text/plain)
2012-06-26 18:50 UTC, johnav 		no flags Details
error_screenshot (62.41 KB, image/png)
2012-06-26 18:52 UTC, johnav 		no flags Details
View All

Description johnav 2012-06-26 18:48:23 UTC 
Created attachment 594570 [details]
icedtea debug logs

Description of problem:

When starting Juniper VPN on Fedora 17 64 bit, gets error applet not initialized

Version-Release number of selected component (if applicable):
- Fedora 17 64 bit
- Firefox 12
- IcedTeaPlugin1.2
- Java 1.7.0_b147-icedtea

How reproducible:

- Login Juniper VPN
- Click on start button to start Network Connect

Steps to Reproduce:
1. Login Juniper VPN
2. Click on start button to start Network Connect
3.
  
Actual results:
Showing applet not initializederror. Please see screenshot
Expected results:
Network Connect should be launched


Additional info:
Comment 1 johnav 2012-06-26 18:50:55 UTC 
Created attachment 594571 [details]
java console logs
Comment 2 johnav 2012-06-26 18:52:38 UTC 
Created attachment 594572 [details]
error_screenshot
Comment 3 johnav 2012-06-27 08:25:28 UTC 
Issue happens when CN in the certificate doesn't match with host name typed in the address bar. When I added CN in the /etc/hosts file and access server using CN, problem resolved.
Note You need to log in before you can comment on or make changes to this bug.