Certificate invalid?

[irongecko]

Hi all, i'm trying to use the profit ui autoupdating version, and the launcher won't start - getting the error "Failed to validate certificate - The application will not be executed"

Using the latest version of java on a fresh vista sp1 install.

Can anyone help me out?

[Kaldran]

It is not invalid, it cannot be validated. Or better: the check for revocation fails.

Go to the Java Control Panel in your System Control and turn off "Check publisher certificate for revocation" (which _is_ turned off by default)

[irongecko]

Check publisher certificate for revocation is already set to off. I tried setting it to on, hitting apply and setting if to off again, but it's still a nogo

Thanks for the speedy reply!

[dansherrill]

What it is saying on mine is that the certificate is invalid. Then if you click on the details button what it says in the details is that one of the files is not valid my guess is that you have a file that has been changed in the updater that has not had the certification attached to it since the change. You can go ahead and accept the file if you turn off some settings but on the defaults it will automatically say failed no matter what the revoke status is. PS Its been this way for about 2 weeks now.

[irongecko]

I can't see any settings to disable the checking etc. The error i'm getting is

java.io.IOException: Invalid keystore format
 at sun.security.provider.JavaKeyStore.engineLoad(Unknown Source)
 at sun.security.provider.JavaKeyStore$JKS.engineLoad(Unknown Source)
 at java.security.KeyStore.load(Unknown Source)
 at com.sun.deploy.security.DeploySigningCertStore$1.run(Unknown Source)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sun.deploy.security.DeploySigningCertStore.loadCertStore(Unknown Source)
 at com.sun.deploy.security.DeploySigningCertStore.load(Unknown Source)
 at com.sun.deploy.security.DeploySigningCertStore.load(Unknown Source)
 at com.sun.deploy.security.ImmutableCertStore.load(Unknown Source)
 at com.sun.deploy.security.TrustDecider.isAllPermissionGranted(Unknown Source)
 at com.sun.javaws.security.AppPolicy.grantUnrestrictedAccess(Unknown Source)
 at com.sun.javaws.LaunchDownload.checkSignedResourcesHelper(Unknown Source)
 at com.sun.javaws.LaunchDownload.checkSignedResources(Unknown Source)
 at com.sun.javaws.Launcher.prepareLaunchFile(Unknown Source)
 at com.sun.javaws.Launcher.prepareToLaunch(Unknown Source)
 at com.sun.javaws.Launcher.launch(Unknown Source)
 at com.sun.javaws.Main.launchApp(Unknown Source)
 at com.sun.javaws.Main.continueInSecureThread(Unknown Source)
 at com.sun.javaws.Main$1.run(Unknown Source)
 at java.lang.Thread.run(Unknown Source)

[Kaldran]

Found the problem:

If you add arguments or properties to the *.jnlp file, it has to be signed as well to be considered safe by java. You do that by having a copy inside the signed main *.jar file. Should work now.

[Bishoy]

i think that's related to java security , so you will go to the java icon (in the task bar) , right click , choose "Open Control Panel" , then under the "Advanced" tab you go under Security node , expand it and uncheck
" Enable list of trusted publishers " , next time you open the application it will ask you if you trust the source , you click yes and there you go ..

Bishoy Harby

[Kaldran]

Originally Posted by Kaldran

If you add arguments or properties to the *.jnlp file, it has to be signed as well to be considered safe by java. You do that by having a copy inside the signed main *.jar file. Should work now.

As messages have to be at least 10 chars long you'll get this completely unrelated sentence in addition, but free of charge.