#266 Can't launch IGB after modifying igb-5GB.jnlp

[David Nix]

Hello Folks,

I'd like to point the igb.jnlp file to load a different igb_prefs.xml that is identical to the standard but contains two additional DAS2 servers:

<server type="das2" name="UofUtahBioinfoCore" url="http://bioserver.hci.utah.edu:8080/DAS2DB/genome" enabled="true" order="8" default="true">
<server type="das2" name="B2B" url="http://b2b.hci.utah.edu:8080/das2gnomex/genome" enabled="true" order="9" default="true"></server></server>

Yet when I modify the igb-5GB.jnlp to point to the new igb_prefs.xml hosted on our web server, IGB won't launch and throws a security error:

JNLPSigningException[Failed to validate signing of launch file. The signed version does not match the downloaded version.]
at com.sun.javaws.jnl.LaunchDesc.checkSigningTemplate(Unknown Source)
at com.sun.javaws.security.JNLPSignedResourcesHelper.checkSignedLaunchDescHelper(Unknown Source)
at com.sun.javaws.security.JNLPSignedResourcesHelper.checkSignedLaunchDesc(Unknown Source)
at com.sun.javaws.security.JNLPSignedResourcesHelper.checkSignedLaunchDesc(Unknown Source)
at com.sun.javaws.Launcher.prepareResources(Unknown Source)
at com.sun.javaws.Launcher.prepareAllResources(Unknown Source)
at com.sun.javaws.Launcher.prepareToLaunch(Unknown Source)
at com.sun.javaws.Launcher.prepareToLaunch(Unknown Source)
at com.sun.javaws.Launcher.launch(Unknown Source)
at com.sun.javaws.Main.launchApp(Unknown Source)
at com.sun.javaws.Main.continueInSecureThread(Unknown Source)
at com.sun.javaws.Main.access$000(Unknown Source)
at com.sun.javaws.Main$1.run(Unknown Source)
at java.lang.Thread.run(Thread.java:744)

Any suggestions? I've attached the modified files. One solution would be to add in these two servers to the standard IGB prefs file. They both contain considerable public datatracks. They used to be in there but no more.

-cheers, David

[David Norris]

Hi David,
There is nothing you can do at the moment to work around this issue since the signed jnlp file is not currently allowing modifications of this value; however, we can "wildcard" this argument in a future release to allow for this flexibility. This change could not be released in a minor version update, so will have to wait for the next major release (IGB 8.2, which we hope to release in the next few months). For now, you would need to manually add these data sources once IGB has launched.

Best Regards,
David

[Ann E. Loraine]

Hi David,

It's possible we can help you solve this sooner than the next release by modifying a server-side configuration file that determines default data sources for IGB - both DAS and QuickLoad.

If you like, we could add your sites to the list of default servers in IGB. The ones that require a password would need to be disabled to avoid disrupting non-HCI users, and so this would mean your users would still have to click "configure" and then use the Data Sources Preferences panel to activate the HCI DAS sources. But at least they would not have to enter the URL manually.

Either way, we'll configure the JNLP in the next release so that you can add a preferences file as an optional argument.

We don't have a firm release date yet for IGB 8.2 but should know fairly soon when that would be -- it's really close. Ideally an alpha will be released by the end of November.

Also I wanted to let you know: We're looking into using native installers either instead of or in addition to Java Web Start as a way to distribute IGB. If you have suggestions, requests, concerns about this, please let us know.

Yours,

Ann