Unsigned Jars in 5.1.2

Classic Servoy
21

rafig:

IT2Be:
That is an old jnlp file Rafi.

Not me, Marcel, check poster, it was Vaj…
:wink:

Rafi

Ah, but you both are in the UK right… :)

22

IT2Be:
Ah, but you both are in the UK right… :)

Didn’t realise it was such a localised issue :D

23

Didn’t realise it was such a localised issue

hahahaha!

24

See http://wiki.servoy.com/x/SpV7 for a comprehensive overview of Servoy i.c.w. Java 6 update 19

Paul

25

Using unsigned 3rd party plugins and/or beans
Unfortunately, in most deployment scenario’s just upgrading to the latest version of Servoy will not be sufficient. If the Servoy Application Server contains 3rd party plugins and/or beans, additional steps are required, see JAR signing for more information. (these steps apply for any used Java version on the server)

Paul, Good information! I would refraze ‘additional steps are required’ into ‘additional steps could be required’.

26

See http://wiki.servoy.com/x/SpV7 for a comprehensive overview of Servoy i.c.w. Java 6 update 19

Brilliant guide. Starting on this now.

27

I would refraze ‘additional steps are required’ into ‘additional steps could be required’.

Marcel,

The phrase is already correct, as it’s under the section “Using unsigned 3rd party plugins and/or beans” with the emphasis on “unsigned”.

I did rephrase a bit to make it more clear though, tnx for pointing it out.

Paul

28

Thanks Paul!!
MUCH appreciated!

29

Hi everybody,

I’m using this thread to introduce our problem, which is also about “Unsigned Jars in 5.1.2”.
We have upgraded our test server to 5.1.2 with Java u20. We use 2 clients with Java u19 and u20. We have signed all our jars using the signing tool of Johan and added “All Permissions” to all our jnlp files.
However we have an issue with a jar file which is not signed. We get a Java warning message at the start which hangs the whole javaw process forever. And when we switch the Java security settings to “Enable - hide warning and run with protections” we get the following launch error:

om.sun.deploy.net.JARSigningException: Found unsigned entry in resource: (http://ag-dev:8080/plugins/servoyguy_sp … ary_en.jar, 1.0)

It is not signed because it’s just a text file and not a class. But Servoy 5.1.2 should handle it, shouldn’t it?!
By switching the Java security setting to “Enable - hide warning and run with protections” and removing the “All Permissions” tags in the plugin jnlp file, it works. But this settings are supposed to be used with previous versions of Servoy.

Any idea?

30

also resources jars should be signed.
does my tool not sign that jar?
Can you give me that jar so that i can test it?

31

It seems to react like with the swingbeans.jar. Has you explained me:

[…]
But swing beans cant really be signed at least there is not really something to sign (there are no classes)
[…]

It’s the same with dictionary_en.jar I think.

Here is the jar: [attachment=0]dictionary_en.jar[/attachment]

Full plugin can be found here: http://www.servoyguy.com/servoy_compone … pro_plugin

dictionary_en.jar (450 KB)

32

thats not the same as the swingbeans.jar (that one is really empty, this one has a resource)
The problem is only that the signerjar tool will skip this one, but it shouldnt do that…

this jar you have to do by hand:

jarsigner -keystore YOURKEYSTORE dictionary_en.jar ALIAS

33

i updated the sign tester tool so it also will sign those jars.

34

Thanks!
We have tried to sign it “manually” using jarsigner but we ended up with another error : 2 different keystore have been used to sign the components described by the jnlp (even if we used exactly the same for both).
So, we will try with your new updated signtester and will let you know if it works.

Cheers.

35

Using the signtester to sign all jars worked fine!
Now with Java u19-20 with full security settings and Servoy 5.1.2, it works for us :D

Thanks Johan.