If the Device Certificate imported into an PCS appliance is signed with SHA256 (SHA2), certificate authentication may fail with this error:
Invalid or expired certificate. Check that your certificate is valid and up-to-date, and try again.
You may also see the
wrong-cert reason string in the
welcome.cgi URL, as in this example:
If a JavaSoft certificate signed with SHA256 (SHA2) is used to re-sign applets, applet launch may fail with this error:
Security Exception. Could not verify signing in resource.
This can happen if the JavaSoft Certificate is imported directly into the PCS appliance and is used to re-sign web controls or Java Applets. This can also happen if the JavaSoft Certificate is not imported, but a JavaSoft Certificate signed with SHA256 (SHA2) is used to sign an internal Java Applet accessed through the URL Rewriter.