Reputation: 1
I'm having a weird SSL issue. I have a dynamically generated page which contains a Java applet linking to a dynamically generated JNPL file. The applet does what it is suppose to do. This all works.
The issue is with the SSL certificate. Browsers have no problem with the certificate looking at static pages or with the dynamically generated page. Only the client side complains when the Java stuff starts that the 'Publisher authenticity can not be verified."
The issue goes away when I use a non-SSL URL to the JNPL file. Is there a work-around for this issue? I'd like to go SSL all the way.
And my jar is code-signed.
Thanks
Upvotes: 0
Views: 615
Reputation: 20134
This error comes when your ssl-certificate was issued from a root-certificate that is not in the java-truststore but is in the browsers truststore.
you can check which certificate-issuers are trusted in your java-vm by using the keytool (comes with the jdk afaik) the truststore for java is usually installed in jre/lib/security
keytool --list -keystore cacerts
lists all certificates that are included in the keystore
Upvotes: 2