Ssl error vmware horizon client 4.7 plus#

Ssl error vmware horizon client 4.7 plus#

To create a new certificate for our Log Insight platform we first need to define the requirements of the certificate which includes host names, key length, algorithm, usage plus a few other things. Either method requires making changes to agent configuration files. Your environment may not have your CA cert(s) installed on your machines and if this is the case then you would either need to role those out first or make a decision to trust any SSL certificate presented by Log Insight servers. It will look within the file system (local certificate store for Windows) for a CA certificate and then validate the Log Insight certificate against the CA. In this configuration the agent will only accept a certificate that is recognised as being issued by a trusted authority. However, if it your agent configuration looks like the screenshot below then there could be significantly more work ahead. In this example we can see our agent is configured to accept any SSL certificate and therefore we can change the SSL certificate on the Log Insight installation without any further work. You can examine an agent configuration file to validate the settings. If SSL is being used for securing agent connectivity then it is important to understand whether a certificate change will be automatically accepted by the agent(s) or whether the issuing CA bundle will need placing on each agent machine to allow connectivity to be re-established. The obvious use is for securing the communications between a users web browser and the Log Insight installation however if you are using the CFAPI protocol within the Log Insight agent(s) then you may also be using the certificate for securing connectivity between the agent(s) and Log Insight server(s). The certificate can be used for several things and depending on how the platform has been configured may mean you need to do more or less work to complete the change. Asses the Impactīefore you change anything it is important to understand what the impact of changing the SSL certificate is on your environment. For some customers this is fine however there normally comes a point when either the certificate expires or a security requirement comes into play that requires the self-signed certificate be replaced.

Log Insight comes configured out of the box with a self-signed certificate that is generated during the installation.

The following process has been illustrated using Log Insight version 4.6.1 however it is also the same for version 4.7.