Posted by Sven Gothel on Feb 23, 2012; 9:42am
URL: https://forum.jogamp.org/SecurityException-no-certificate-for-libgluegen-rt-so-tp3767870p3769214.html

On 02/23/2012 10:36 AM, gouessej [via jogamp] wrote:
>
>
> You're right but in the short term it is nice to have a workaround instead of
> "panicking". Moreover, when using Java Web Start, if you use different
> certificates, you have to use several JNLP files and then the final user has
> to click several times to confirm if he uses only a single application
> relying on JOGL.

In case you need your application to be signed - yes!

If you have a game and pure Java
you don't need your application/applet to be signed,
it's enough to have the JogAmp modules (gluegen/jogl) being signed.

Eg. our jogl-demos jar file is not signed,
as described on the applet test page and jogl-demo's page.

Sure, if you need something else to be signed,
your recommended process is best.

~Sven