Overview > JSSE Integration

JSSE Integration

Belongs to following categories: Integration, ULC5.2,

Purpose

This contribution demonstrates how to integrate JSSE (Java Secure Socket Extension) with ULC.

JSSE can be used to

add HTTPS support to JRE 1.3.
replace the browser based HTTPS support used by the Java plug-in for JRE 1.3.

Note that ULC does not support browser based HTTPS on Nescape / Mozilla. See also PR830 in the ULC problem report database. So this contribution provides a workaround for PR830.

Resources

Try out the JSSE integration as Applet.
Try out the JSSE integration as JNLP application. Note that this is a JRE 1.3 specific JNLP file. See also remarks below.
Download the complete source code.
Download the self-contained war file.

How to use

Invoke JsseIntegrationUtilities.installJsseIfNecessary() in your launcher. This installs JSSE if there is currently no or only browser based HTTPS support.

public class JsseAppletLauncher extends DefaultAppletLauncher {
    public void init() {
        JsseIntegrationUtilities.installJsseIfNecessary();
        super.init();
    }
}

How to deploy

The code for this contribution is separated into two installables:

jsseintegration-sample-client.jar: contains the implementation for JsseIntegrationUtilities.installJsseIfNecessary().
jsseintegration-client.jar: installs JSSE and therefore needs full permissions.

Note that we signed the jsseintegration-client.jar file in order to get full permissions in Applet deployment.

Notes for Java Web Start 1.0.1 Deployment

Unfortunately the Java Web Start implemention that is compatible with JRE 1.3 installations has a bug that forces you to provide separate JNLP files if want to download JSSE only when needed. For more information see

Java bug 4809201.

This leads to the following JNLP file for JRE 1.3:

<?xml version="1.0" encoding="ISO-8859-1"?>
<jnlp spec="1.0+" codebase="$$context" href="application.jnlp">
    <information>
        <title>jsseintegration</title>
        <vendor>Canoo AG</vendor>
        <description>Sample application of jsseintegration extension.</description>
        <homepage href="http://www.canoo.com/ulc"/>
        <icon href="application.gif" width="48" height="48"/>
    </information>    <resources>
        <j2se version="1.3"/>
        <jar href="lib/jsseintegration-sample-jnlp-client.jar" main="true"/>
        <extension name="JSSE Integration" href="$$context/jsseintegration.jnlp"/>
        <extension name="JSSE" href="$$context/jsse.jnlp"/>
        <extension name="ULC" href="$$context/ulc.jnlp"/>
    </resources>
    <application-desc main-class="com.canoo.ulc.community.jsseintegration.client.environment.jnlp.JsseJnlpLauncher">
        <argument>https://www.canoo.com/jsseintegration/application</argument>
        <argument>60</argument>
        <argument>WARNING</argument>
    </application-desc>
</jnlp>

Note that JSSE and the JSSE Integration are deployed as separate component extensions as they need full permissions and are signed with different code certificates. All other deployables run with standard JNLP permissions.

Note also that Java Web Start 1.0.1 does not support resource download over HTTPS. So you have to deploy the client part of your ULC applicaton over HTTP. However, with this contribution you are able to connect to the server part of your ULC application over HTTPS (note the HTTPS ULC application URL in the above JNLP file).

Compatibility

The described functionality has been developed and tested using JDK 1.3.1_13, JDK 1.4.2_05, JDK 1.5 and ULC 5.2.1.

Author

daniel

one comment (by Jitendra) | post comment

labels

Category:	ULC5.2
Category:	Integration

attachments

jsseintegration.war (1650181)
jsseintegration.zip (567056)

Created by daniel. Last edited by admin, 6 years and 243 days ago. Viewed 13,374 times. #17

[diff] [history] [edit] [rdf]

Jitendra, one year and 100 days ago.

Lieber Karl,wir sehen den Punkt mit den Niveaus. Wir haben darüber dsriutiekt und uns aus folgenden Gründen für die Untersuchung in Wachstumsraten entschieden:1) Wir wollten einen Bezug zur Literatur zur Konvergenz der Inflationsraten — schliesslich hat die Zentralbank explizit oder implizit ein Inflations- kein Preisniveauziel.2) Die üblichen Tests auf Vorliegen von Nicht-Divergenz (z.B. Kointegration zweier für sich genommen nicht-stationärer Reihen, deren Linearkombination wieder stationär ist oder der Test auf gemeinsame und idiosynkratische Triebkräfte im Panel (PANIC)) sind i.d.R. für den Stationaritätsgrad I(1) abgeleitet worden, d.h. trendbehaftete oder sehr persistenten Zeitreihen, die durch einfache Differenzenbildung in stationäre Zeitreihen umgewandelt werden können (konstanter Erwartungswert, endliche Varianz, begrenzte Autokorrelation). Die Preisniveaus sind aber in der Regel I(2), d.h. man muss sie zweimal differenzieren, um eine stationäre Reihe zu bekommen.3) Im Prinzip gibt es auch Sachen für I(2)-Reihen — ehrlich gesagt sollten wir das mal machen Also vergiß meine halbherzige Entschuldigung von oben!4) USA/Deutschland. Wir haben die Panels ausgewählt eben weil sie schon länger eine Währung haben. Wir suchten eine Art “benchmarking” für Divergenzen in “funktionierenden” Währungsräumen.Gruß, Uli