Documentation Center

Enabling SSL encryption of the connection from microservices to your Microsoft SQL Server database

By default, Content Delivery microservices are configured to connect to a Microsoft SQL Server database without using encryption. If you would prefer to encrypt your connections, you can do so by changing your microservice configurations. This causes the JDBC Driver to use encryption.

Before you begin

In order to use encryption, your infrastructure must meet one of the following requirements:
  • Your Java application has appropriate encryption keys added to the trust store.
  • The server certificate is trusted.

About this task

To learn more about connecting with SSL encryption, refer to this resource: https://learn.microsoft.com/en-us/sql/connect/jdbc/connecting-with-ssl-encryption?view=sql-server-ver16

Procedure

  1. Ensure that the encrypt property in the Storage Layer configuration file, cd_storage_conf.xml, of each microservice that connects to a Microsoft SQL Server database, resolves to the value true. (The environment variable associated with this property is dbencrypt).
  2. Ensure that the encrypt property in the caching configuration file, cache-conf.xml, of each microservice that connects to a Microsoft SQL Server database, resolves to the value true. (The environment variable associated with this property is dbencrypt).
  3. If your Content Deployer connects to a Microsoft SQL Server database, ensure that the encrypt property in the configuration file of the Content Deployer, deployer-conf.xml, resolves to the value true. (The environment variable associated with this property is dbencrypt).
  4. Restart all affected microservices.