my dog learned polymorphism*
The moose likes JNLP and Web Start and the fly likes using https by jsw-client Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Java 8 in Action this week in the Java 8 forum!
JavaRanch » Java Forums » Java » JNLP and Web Start
Bookmark "using https by jsw-client" Watch "using https by jsw-client" New topic
Author

using https by jsw-client

Karl Brodowsky
Greenhorn

Joined: Jul 06, 2004
Posts: 1
An interesting combination is using https by the java-client that has been started using jws/jnlp. This way a safe communication mechanism that goes through most firewalls is possible between client and its server. But https requires a public certificate, which must be trusted in order to go on with the communication. For this purpose, the java world knows the concept of the truststore, which contains all the certificates that are trusted. But this truststore is specified by a system property as a file name, which is hardly compatible to the typical java-web-start situation, where there is no common, platform independent absolute path for a file which is ideally even writeable in order to download and install new trusted certificates, if approved by the user.

Is there any best practice how to solve this kind of issue?

What would work is this: Try serveral directories, download certificate, store it in truststore in one of these directories and set the system property appropriately thereafter. But it is not really smooth. Any ideas?

Best regards,

K.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: using https by jsw-client
 
Similar Threads
Queries on role of files .keystore and CAKey.pem while moving the site to https?
configuring Tomcat for SSL
Default keyStore/trustStroe for the tomcat server
regarding cacerts from JAVA_HOME\jre\lib\security
Web Service SSL Client