Updated 28Feb2019 to remove App Layering version info. The process documented works for 4.x, 18xx, and 19xx versions.

After importing the appliance, I logged into the CentOS console and configured the basic networking stuff, as shown in Figure 1.

Next, I used Internet Exploder, I mean Explorer (IE), to start the rest of the configuration steps.

After setting the passwords for the three management accounts, the next item was the HTTP Certificate Settings.

One of the awesome benefits of being a CTP is that DigiCert gives the CTPs almost unlimited SSL certificates. Thank you very much, DigiCert.

The first thing I needed to do was generate a CSR file to give to DigiCert for my certificate request. Since the ELM is based on CentOS Linux, it has OpenSSL included. I found a helpful article from DigiCert support that automatically generates the required OpenSSL command, as shown in Figure 2.

I use PuTTY to log on to the console as root and pasted in the OpenSSL command that DigiCert supplied, as shown in Figure 3.

Note: There is a bug in a fresh import of the 4.2 appliance where the wizard used to change the three account’s passwords does not change the password for root. To login as root, use the default password.

Next, I used WinSCP to download the two files created, as shown in Figure 4.

I used the CSR file to request my SSL certificate from DigiCert.

Once I received my ZIP file, I extracted the certificate files to the same folder I placed the CSR and KEY files downloaded from the ELM appliance, as shown in Figure 5.

Using Notepad++, I opened the CRT and KEY files and created a new blank unidesk_labaddomain_com.pem file. I then copied the KEY file contents first into the PEM file and then added the CRT file to the bottom of the PEM file, as shown in Figure 6.

Back in the browser interface for the ELM appliance, click Edit for HTTP Certificate Settings, as shown in Figure 7.

Click Upload as shown in Figure 8.

Browse to the PEM file created earlier, select it and click Open, as shown in Figure 9.

Verify the Uploaded Certificate information is correct. If it is, click Save, as shown in Figure 10. If the information is not correct, you may need to recreate the PEM file or receive a new SSL certificate.

Click Yes to restart the webserver, as shown in Figure 11.

I created a DNS A record to match the SSL certificate, as shown in Figure 12.

Once the browser window refreshes, exit IE, restart IE, and browse to https://FQDN of the ELM appliance as shown in Figure 13.

Notice there are no SSL certificate errors even though the PEM file did not contain any Intermediate or Root certificate information.

I want to give a shout-out to Kyle at DigiCert support for all the time he spent with me working through this process.

Thanks

Webster