FoxT Control Center (FCC) installation gives certificate failure messages and users attempting to log in to FCC are presented with the error:
java.security.cert.CertificateException: no name matching found
This issue is caused when the hostname in the certificate and that returned by the DNS resolver are not the same.
This situation can depend on a number of factors, including:
Resolution / Workaround
To avoid errors of this kind, use the FQDN in certificates, for the AdminServerURL parameter in bcc.properties, and as the first name for the host in /etc/hosts.
Having the FQDN in the host certificate may be a requirement for the end-user's Web Browser to accept the certificate (once the CA issuer is known or accepted). However that will only work if the resolver (on the user's workstation) will return the FQDN of the server (in both forward and reverse lookups).
Still have questions? We can help. Submit a case to Technical Support.