Page 2 of 2

Re: Smart Client digital signature issue

PostPosted: Thu Feb 20, 2014 1:19 pm
by Harjo
The yellow balloon is a bug in Java. That will probably fixed in next java version. Which malefic message do you get?

Re: Smart Client digital signature issue

PostPosted: Thu Feb 20, 2014 2:48 pm
by jcompagner
you have to see them in the root ca list that you can lookup in de java preferences

Re: Smart Client digital signature issue

PostPosted: Thu Feb 20, 2014 3:41 pm
by pasin
Harjo wrote:The yellow balloon is a bug in Java. That will probably fixed in next java version. Which malefic message do you get?

My malefic message i think it's just the yellow balloon (look the image)
yello baloon.png
Malefic message
yello baloon.png (21.37 KiB) Viewed 9008 times


jcompagner wrote:you have to see them in the root ca list that you can lookup in de java preferences

So if i find my certificate under the certificate-type "secure certificate" into the java preference my root's certificate is correct, otherwise it isn't.. right?
(i'm not sure but we are talking about the machine that i use to certificate my application, do you confirm?)

Re: Smart Client digital signature issue

PostPosted: Thu Feb 20, 2014 4:08 pm
by jcompagner
so it does start normally you only get that screen?
thats the java bug

Re: Smart Client digital signature issue

PostPosted: Thu Feb 20, 2014 4:28 pm
by pasin
jcompagner wrote:so it does start normally you only get that screen?
thats the java bug

Yes, now the situation is this.
I can solve this yellow balloon only by installing my personal certificate in each computer where my application run, but because this is not possible I'ill wait the java update.

Thanks a lot to all
Alberto

Re: Smart Client digital signature issue

PostPosted: Thu Feb 20, 2014 9:33 pm
by Harjo
Or just hit the selection box once, and all is set!

Re: Smart Client digital signature issue

PostPosted: Fri Feb 21, 2014 9:33 am
by ROCLASI
Depending on the permissions of the system user you may or may not have this checkbox.
If you don't have this checkbox you will always get this dialog when you launch Servoy client.

Re: Smart Client digital signature issue

PostPosted: Fri Feb 21, 2014 1:54 pm
by robrecht
Are you sure the yellow balloon is still the java bug?
I saw a lot of posts on this forum in the servoy Jira some time ago and talking about this bug which would be fixed in java update 51, mid january
Is there a case available at java support where we can follow this issue?

Thanks
Robrecht

Re: Smart Client digital signature issue

PostPosted: Fri Feb 21, 2014 2:28 pm
by Harjo

Re: Smart Client digital signature issue

PostPosted: Mon Feb 23, 2015 1:34 pm
by gdurniak
We just updated to Servoy Server 7.4.3, and still get a bunch of Java Warnings for Smart Client

Can this ever be fixed ? Note: it does seem that adding the Server IP and Port to the Java Exceptions list at least allows the Client to open

greg


Java Version 7 Update 51:

The certificate used to identify this application has expired

This application will be blocked in a future Java security update because the JAR file manifest does not contain the Permissions attribute.

Part of the application is missing a digital signature

Although the application has a digital signature, the application's associated file (JNLP) does not have one.

Note to the Publisher: Security features to prevent unauthorized redistribution of your Java application will cause this application to be blocked in the future

Details ( Certificate )
Version: V3
Issuer: CN=thawte SHA256 Code Signing CA, O="thawte, Inc.", C=US
Validity: [From: Tue Dec 10 00:00:00 UTC 2013, To: Sat Dec 09 23:59:59 UTC 2023]
Subject: CN=Servoy B.V., OU=SERVOY, O=Servoy B.V., L=Amsterdam, ST=Noord Holland, C=NL

Re: Smart Client digital signature issue

PostPosted: Mon Feb 23, 2015 2:11 pm
by jcompagner
the expired one should not be happening on 7.4.3 (maybe that java starts it up once with the old onces before it gets the new onces?)

the jnlp one can only be fixed by by changing the property of "servoy.vmClientArgs" on the admin page, if you have there a default value then you need to make that a space only.
It shouldn't contain: -XX:SoftRefLRUPolicyMSPerMB=3600000

this has a side effect that the performance could be a bit worse, because less caching is done.