Tested_Java_Release : 1.5.0-beta2-b47
Tested_bundles_Location :
promoted builds: /net/koori.sfbay/p/jdk07/jdk/1.5.0/beta2/b43/bundles
Tested_Machine_Name : moremoney/blueski
Tested O/S : winxp/solaris10
Problem Description :
If corrupted trusted.cacerts and trusted.jssecacerts stores exist at user level, then security exception is getting thrown while running the signed and https applications. Getting security exception is correct behavior but the behavior is not consistent.
Following steps will explain in detail the inconsistency noticed:

1) Copy /net/sqesvr-nfs/global/nfs/deployment2/jitu/trusted.cacerts.corrupted to
<user_dep_home>/security (<user_home>/.java/deployemnt/security on unix and
C:/Documents and Settings/Application Data/<user>/Sun/Java/Deployment on
windows)

2) rename trusted.cacerts.corrupted to trusted.cacerts

3) Open Java Control Panel > Security > Certificates

4) Error Dialog should be there. Click on more details ,exception
java.io.Exception: Inavlid keystore format should be there

5) Try to run the signed applet
http://sqeweb.sfbay.sun.com/deployment1/deployment_tiger_exec_ws/deployment/test
s/RSATestsuite/pluginhtml-default/Vergrant.html
Security exception should get thrown
java.io.Exception: Inavlid keystore format should be there

6) Click on the link below to run the https applet
http://sqe-jpi-01.sfbay.sun.com:8080/tests/https/pluginhtml-default/GP.html
Security exception will get thrown

Remove the corrupted trusted.cacerts store from the <user_dep_home>/security
7) Copy
/net/sqesvr-nfs/global/nfs/deployment2/jitu/trusted.jssecacerts.corrupted to
<user_dep_home>/security (/<user_home>/.java/deployemnt/security on unix and
C:/Documents and Settings/Application Data/<user>/Sun/Java/Deployment on
windows)

8) rename trusted.jssecacerts.corrupted to trusted.jssecacerts

Try to run both the above mentioned applet. Only in case of https we are
going to have security exception

Now when the security exception is thrown in case of corrupted trusted.cacerts there is proper exception dialog pop-up,no matter the "Show applet lifecycle exceptions" is checked or not. While in case of corrupted trusted.jssecacerts the exception pop-up will only be there only and only if "Show applet lifecycle exceptions" on Java control panel is checked
Same can be noticed while running the JNLP applications(In JAWS like plug-in there is no way to switch on the exception dialog)
 
----------
since there is good reason for the inconsistancey between plugin and webstart, I am closing as will not fix.

###@###.### 2004-05-26