Back=right mouse click.
HTTP > Applets and ActiveX > Settings | Java Applets
The process of instrumenting a signed applet (as configured in the Applet Instrumentation Settings page) invalidates the applet's signature. IWSVA strips the broken signature from the applet, leaving it unsigned—it no longer has the permissions it requires for correct operation in the client's browser. To address this, you can have IWSVA re-sign all instrumented applets that were found to be validly signed.
Note: A re-signing certificate and private key pair must be available on the IWSVA machine, with the proper policy settings selected.
Leave the applet unsigned—IWSVA takes the action specified in Java Applet Security Rules for unsigned applets.
Re-sign the applets—If the applet was signed and the original signature of the applet was valid (IWSVA found nothing wrong), and if you have configured IWSVA with a private key and a corresponding certificate, you can have IWSVA re-sign the applet by using the private key. IWSVA will process re-signed applets according to the settings specified for signed applets on the Java Applet Security Rules page.
Specify the location of the file containing the private key and its corresponding certificate. It must be in PKCS#12 (also known as PFX format under Windows) and located somewhere accessible to the client machine being used. The password will be used only to open the file – it will not be used by IWSVA to store the file on the IWSVA host machine.
The Public-Key Cryptography Standards (PKCS) are a set of standards for public-key cryptography. PKCS #12 is a portable format for storing or transporting a user's private keys, certificates, miscellaneous secrets, and so on. The two most common file extensions for this format are:
.p12
.pfx
Java Applets
Applet Instrumentation Settings
About Digital Signatures
