Hi All
We got the news that renewing the code certificate, the process has changed (at least when having a certificate form Global Sign). In short, we do not get mailed a .pfx file anymore, but a physical USB stick containing software to get an USB token (whatever that is). But it does not seem to be possible to create a .pfx file and therefor no keystone file. And this is a prerequisite to use the Code Signer developed by Patrick Talbot and brakes the currently used workflow. The process with the USB token using Java Development Kit (suggested) does not allow for multiple .jar files signing, but only one bey one. At least this is our current knowledge as far as we understand it.
Here are two links to this subject (one in german):
https://magazin.sslmarket.de/inpage/cod ... -geregelt/
https://casecurity.org/wp-content/uploa ... igning.pdf
As we are afraid that the Servoy applications will stop working after the expiration date of the certificate, we would be very happy to hear about your experience and help on how to solve that problem as we are quite in a hurry (certificate expiring soon).
Thanks and best regards,