We updated our wildcard certificate from SHA1 to SHA2 yesterday due to Chrome 42's shunning of SHA1 certificates and imported the new cert into our JSS. Now, Casper Focus gives us an error that the cert is in valid, even though the web interface is happy as a clam. If I roll back to my SHA1 cert (still valid until tomorrow afternoon) Focus works like a champ. We are on 9.65 and all I'm doing is uploading a PFX/P12 through the web interface under Apache Tomcat settings, then restarting Tomcat with the DB utility. Anyone else have issues with SHA2 and Focus? Any chance this is fixed in 9.7?
Support call fixed it - cert needed to be re-exported via certificates snap-in in MMC with the private key and "Include all certificates in the certification path if possible" checked. Exporting through IIS 7.5 manager was not sufficient, even thought the web interface didn't complain at all.