Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.java.programmer > #27474 > unrolled thread
| Started by | Andreas Leitgeb <avl@gamma.logic.tuwien.ac.at> |
|---|---|
| First post | 2014-02-07 15:04 +0000 |
| Last post | 2014-05-27 11:30 +0000 |
| Articles | 3 — 3 participants |
Back to article view | Back to comp.lang.java.programmer
difficulties with using signed jnlp template Andreas Leitgeb <avl@gamma.logic.tuwien.ac.at> - 2014-02-07 15:04 +0000
Re: difficulties with using signed jnlp template adil.tiadi@gmail.com - 2014-05-27 03:34 -0700
Re: difficulties with using signed jnlp template Andreas Leitgeb <avl@auth.logic.tuwien.ac.at> - 2014-05-27 11:30 +0000
| From | Andreas Leitgeb <avl@gamma.logic.tuwien.ac.at> |
|---|---|
| Date | 2014-02-07 15:04 +0000 |
| Subject | difficulties with using signed jnlp template |
| Message-ID | <slrnlf9tf8.ngg.avl@gamma.logic.tuwien.ac.at> |
I'm having difficulties with my signed jnlp template file. I have already read the obvious literature, e.g.: http://docs.oracle.com/javase/7/docs/technotes/guides/jweb/signedJNLP.html but that didn't work/help me with that problem. A particular extra twist may be relevant, namely that there is some extra webapp that serves the jnlp-file subst'ing some $$varname strings (e.g. $$codebase) and stripping all new-lines on the way (while leaving all the excessive tabs and whitespaces intact, that some ant-task cared to produce into it). That means, the jnlp delivered to the client machine isn't the same as the one placed on the server. Our approach therefore was to download the jnlp-file (mimicking a client) through that jnlp-serving webapp from the test-system, then substitute all relevant parts by *, add that to the main jar file (as JNLP-INF/APPLICATION_ TEMPLATE.JNLP) and finally sign and deploy the jar-file on the test-system. And still, the client (Java 7!) refused to start the app. The JNLPSigningException that is thrown says (my own translation, the official English verbiage may vary): "signature of the start file could not be verified. The signed version doesn't equal the downloaded version" The German verbiage "stimmt nicht überein" really means un-equality rather than (as expected) a failed pattern match, but that might be mere hair-splitting. The exception is thrown from: at com.sun.javaws.jnl.LaunchDesc.checkSigningTemplate which may or may not imply that it at least noticed that we're indeed using a template... Any ideas?
[toc] | [next] | [standalone]
| From | adil.tiadi@gmail.com |
|---|---|
| Date | 2014-05-27 03:34 -0700 |
| Message-ID | <e3bb641e-c9fb-419c-838c-27f098fcb978@googlegroups.com> |
| In reply to | #27474 |
Hi, I had the same trouble... Did you fix it? If yes, please give us your fix. Thank you, Adil
[toc] | [prev] | [next] | [standalone]
| From | Andreas Leitgeb <avl@auth.logic.tuwien.ac.at> |
|---|---|
| Date | 2014-05-27 11:30 +0000 |
| Message-ID | <slrnlo8tr8.bi9.avl@login.logic.tuwien.ac.at> |
| In reply to | #28569 |
adil.tiadi@gmail.com <adil.tiadi@gmail.com> wrote: > I had the same trouble... Did you fix it? If yes, please give us your fix. Nope, not yet, but it's still on my todo-list.
[toc] | [prev] | [standalone]
Back to top | Article view | comp.lang.java.programmer
csiph-web