odama94 wrote:My bad. I thought you meant that you were including the JNLP in the Jar before seeing the 'certificate popup'.
If you are asking why I tried to do what was outlined in section 5.4.1, it was to see if it would solve my issue, of getting the certificate popup when I downloaded my web start application to not appear.
.. As I had mentioned in my initial post, the reason the certificate popup ..What is the exact text of that pop-up?
[..] which alerts us to the fact the one or more components of our webstart application is not signed
odama94 wrote:[..] popup specifically says that it's the JNLP file that is not signed
odama94 wrote:[..] the reason the certificate popup shows is because the main JNLP file, which is auto generated on the back end, is not signed
odama94 wrote:[..] "The application's digital signature cannot be verified. Do you want to run the application?"If the last one is the real message, you'd better buy a good dictionary and/or a book about certificates and security.
If the last one is the real message, you'd better buy a good dictionary and/or a book about certificates and security.Well I'm going to insult not your straightness, but your knowledge and reading abilities.
There's just no trust chain to a CA, anyone can home-make a certificate telling he's Microsoft, that doesn't make it true.
PS: don't bother insulting me for my straightness, I won't bother answering.
The popup should be only triggered by unsigned jars, jnlp can either be signed or not.WRONG. Everything can be signed and validated, on Java 6u10+ if the JNLP (and uses properties?) is not signed this will popup.