Install FXCL EKM
To maintain system security, install and operate only copies of FXCL that you get directly from Futurex. A member of the Solutions Architect team provides these files directly, or you can download them on the Futurex Portal or equivalent Futurex-operated file distribution platform. Perform the following steps to install FXCL Extensible Key Management (EKM):Download or copy the
fxcl-x.x.x-win64.zip file to the computer that runs the Microsoft SQL Server instance.Install Authenticode CA Certificate in Windows Certificate Store
Select [ View Certificate ]. You should see that the “Futurex, L.P.” certificate was issued by “Sectigo Public Code Signing CA EV R36”.
Select the “Automatically select the certificate store based on the type of certificate” option and click [ Next ].
Configure FXCL EKM
Perform the following steps to configure FXCL EKM:Create the
C:\FX-Logs directory. The FXCL EKM configuration file outputs content to FXCL EKM logs to the C:\FX-Logs\ directory.Open the
In the Windows Store TLS settings section, make the following changes as shown in the following sample file:
config.json file for editing, and make the following changes:| Parameter | Required configuration |
|---|---|
| log_file | Set the define to point to the C:\FX-LOGS\fxcl-ekm.log directory |
| host | Set the define to point to the IP and port of the network-connected KMES Series 3 device |
| Parameter | Required configuration |
|---|---|
| ca | Set the define to the location of a PEM file containing a list of trusted CA certificates. |
| p12 | Set the define to the location of a PKCS #12 file containing the Microsoft SQL Server client certificate and private key. |
| p12_pass | Set the define to the password the PKCS #12 file is encrypted under. |
FXCL EKM version 1.8.32 added the ability to configure default key group names for symmetric and asymmetric operations. Users must manually create the key groups on the KMES before defining the default key group names in the FXCL EKM configuration file. If the configuration is set but the key group does not exist, the key creation commands in Enable TDE in Microsoft SQL Server by using EKM will fail.
JSON

