The Connection Server instance or security server that has the smart card connected cannot perform certificate revocation checking on the server's TLS certificate unless you have configured smart card certificate revocation checking.
Certificate revocation checking might fail if your organization uses a proxy server for Internet access, or if a Connection Server instance or security server cannot reach the servers that provide revocation checking because of firewalls or other controls.
Make sure the CRL file is up to date.
Horizon 7 supports certificate revocation checking with certificate revocation lists (CRLs) and with the Online Certificate Status Protocol (OCSP). A CRL is a list of revoked certificates published by the CA (Certificate Authority) that issued the certificates. OCSP is a certificate validation protocol that is used to get the revocation status of an X.509 certificate. The CA must be accessible from the Connection Server or security server host. This issue can only occur if you configured revocation checking of smart card certificates. See Using Smart Card Certificate Revocation Checking.
- Create your own (manual) procedure for downloading an up-to-date CRL from the CA website you use to a path on your Horizon 7 server.
- Create or edit the locked.properties file in the TLS/SSL gateway configuration folder on the Connection Server or security server host.
For example: install_directory\VMware\VMware View\Server\SSLgateway\conf\locked.properties
- Add the enableRevocationChecking and crlLocation properties in the locked.properties file to the local path to where the CRL is stored.
- Restart the Connection Server service or security server service to make your changes take effect.