One of the first things you should do, is to configure the communication between the HCL SafeLinx Administration client and the HCL SafeLinx Access Manager, so that it takes place in an encrypted and secure manner. For this, only a few simple steps are needed.

If you are planing to deploy HCL Nomad and you are unsure about the hardware needed for the HCL SafeLinx server, make sure to read the recently published knowledge base article "HCL SafeLinx Performance for Nomad". It offers important performance insights for HCL SafeLinx and HCL Nomad, and shows just how cost-effective HCL SafeLinx is.

If you are using HCL SafeLinx and you cannot access your websites using “HTTPS” and you see the following error in the HCL SafeLinx “wg.log” log file: PKCS12_parse failed, return 587686001 (error:23076071:PKCS12 routines:PKCS12_parse:mac verify failure Then, most likely, either you are using the wrong password for the “P12” file, database where your SSL certificates reside, or your HCL SafeLinx Server is installed on Linux and the password for the “P12” file contains some special characters that need to be escaped.