Hi, Just wondering if anyone else has run across this roadblock before. Went home las night, everything workign fine. Came in this morning, heaps of irate users - no access to files! The webviewers in the solution use the Java applet. However, this morning webviewers are displaying a "can't be used in untrusted" mode error. A dialog pops up saying publisher cannot be verified, with an exception of "java.security.cert.CertPathValidatorException: Certificate has been revoked". Clicking he details button gives.

sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: Certificate has been revoked

at sun.security.validator.PKIXValidator.doValidate(Unknown Source)

at sun.security.validator.PKIXValidator.doValidate(Unknown Source)

at sun.security.validator.PKIXValidator.engineValidate(Unknown Source)

at sun.security.validator.Validator.validate(Unknown Source)

at sun.security.validator.Validator.validate(Unknown Source)

at com.sun.deploy.security.TrustDecider.isAllPermissionGranted(Unknown Source)

at sun.plugin2.applet.Plugin2ClassLoader.isTrustedByTrustDecider(Unknown Source)

at sun.plugin2.applet.Plugin2ClassLoader.getTrustedCodeSources(Unknown Source)

at com.sun.deploy.security.CPCallbackHandler$ParentCallback.strategy(Unknown Source)

at com.sun.deploy.security.CPCallbackHandler$ParentCallback.openClassPathElement(Unknown Source)

at com.sun.deploy.security.DeployURLClassPath$JarLoader.getJarFile(Unknown Source)

at com.sun.deploy.security.DeployURLClassPath$JarLoader.access$700(Unknown Source)

at com.sun.deploy.security.DeployURLClassPath$JarLoader$1.run(Unknown Source)

at java.security.AccessController.doPrivileged(Native Method)

at com.sun.deploy.security.DeployURLClassPath$JarLoader.ensureOpen(Unknown Source)

at com.sun.deploy.security.DeployURLClassPath$JarLoader.<init>(Unknown Source)

at com.sun.deploy.security.DeployURLClassPath$3.run(Unknown Source)

at java.security.AccessController.doPrivileged(Native Method)

at com.sun.deploy.security.DeployURLClassPath.getLoader(Unknown Source)

at com.sun.deploy.security.DeployURLClassPath.getLoader(Unknown Source)

at com.sun.deploy.security.DeployURLClassPath.getResource(Unknown Source)

at sun.plugin2.applet.Plugin2ClassLoader$2.run(Unknown Source)

at java.security.AccessController.doPrivileged(Native Method)

at sun.plugin2.applet.Plugin2ClassLoader.findClassHelper(Unknown Source)

at sun.plugin2.applet.Applet2ClassLoader.findClass(Unknown Source)

at java.lang.ClassLoader.loadClass(Unknown Source)

at java.lang.ClassLoader.loadClass(Unknown Source)

at java.lang.ClassLoader.loadClass(Unknown Source)

at sun.plugin2.applet.Plugin2ClassLoader.loadCode(Unknown Source)

at sun.plugin2.applet.Plugin2Manager.createApplet(Unknown Source)

at sun.plugin2.applet.Plugin2Manager$AppletExecutionRunnable.run(Unknown Source)

at java.lang.Thread.run(Unknown Source)

Caused by: java.security.cert.CertPathValidatorException: Certificate has been revoked

at sun.security.provider.certpath.PKIXMasterCertPathValidator.validate(Unknown Source)

at sun.security.provider.certpath.PKIXCertPathValidator.doValidate(Unknown Source)

at sun.security.provider.certpath.PKIXCertPathValidator.engineValidate(Unknown Source)

at java.security.cert.CertPathValidator.validate(Unknown Source)

... 32 more

Has it been revoked - how would I check - can it be bypassed?

Is there something wnky on the server?

FYI - I've done a fresh reinstall of the latest version of SuperContainer (2.863). Access via a web browser gives the same issue, so I'm assuming that it's external to FileMaker and definteily

BTW, have just been through 20 files, adding "?style=noapplet" to the end of every URL ;-)

BTW, have just been through 20 files, adding "?style=noapplet" to the end of every URL ;-)

Heh, this is definitely one way to curtail Java applet signing issues... So, I am assuming you have a self-signed certificate being used on the server machine on which SuperContainer is being hosted? It could be the case that the certificate that is in your keystore is now invalid (but this is just a shot in the dark).

If this is the case, try replacing your existing certificate with another certificate that has not expired.

Here are a few links that discuss resolving your issue by replacing the keystore with a new one and other solutions.

Regards,

Nope. Not a self-sign cert. Will look at the other solutions you suggest.