1 Reply Latest reply on Oct 24, 2011 11:20 PM by 817614

    Certificate not accepted without a reboot

      During test the build system generates new self signed jars with a new certificate each time. If you load an application with a self-signed certificate at time t0 and then at time t1 load it with the same jars signed with a new certificate from the same DN, ... except for the timestamp. The application will not load and a security exception is raised about an invalid signature. Is this a known issue meaning that then new certificates come out users have to restart the browser if they were running an application?