Managing Configuration Files in DSG on

Configuring the gateway.json file

Mon, 01 Jan 0001 00:00:00 +0000

This section describes global configuration settings that apply across all DSG nodes in a cluster. These settings extend the options available in the Global Settings tab by providing additional system‑level controls.

The gateway.json file includes configurations, such as, setting the log levels, enabling learn mode, and so on.

Note: It is recommended that configuration changes are made on the ESA and then deployed to the DSG nodes in the cluster

Configuring the features.json file

Mon, 01 Jan 0001 00:00:00 +0000

The features.json file is one of the files in the Protegrity Data Security Gateway (DSG) configuration. By adding or removing flags to this file, users can enable or disable specific behavior in the product.

Sample features.json file

The following snippet shows the default parameters configured in the features.json file.

{
 "features": [
 "enhanced-http-transaction-metrics",
 "disable-sftp-client-key-check",
 "normalize-time-labels",
 "enhanced-lock-filename"
 ]
}

The following table provides descriptions of the feature flags that can be configured in the features.json file.

Configuring the pycore.ini file

Mon, 01 Jan 0001 00:00:00 +0000

Accessing the pycore.ini File

Login to the DSG Web UI.
Navigate to Settings > System > Files.
Open the pycore.ini file.

Sample pycore.ini file

The following represents a sample pycore.ini file.

###############################################################################
# Resilient Package Sync Config
# -----------------------------
# Protector configuration
# ----------------------------- 
[protector]

# Cadence determines how often the protector connects with ESA / proxy to fetch the policy updates in background.
# Default is 60 seconds. So by default, every 60 seconds protector tries to fetch the policy updates.
# If the cadence is set to "0", then the protector will get the policy only once.
#
# Default 60.
cadence = 60
###############################################################################
[sync]

# Protocol to use when communicating with the service providing Resilient Packages.
# Use 'https' for ESA or 'shmem' for local shared memory.
protocol = https

# Host/IP to the service providing Resilient Packages
host = <hostname>

# Path to CA certificate
ca = /mnt/ramdisk/certificates/mng/CA.pem

# Path to client certificate
cert = /mnt/ramdisk/certificates/mng/client.pem

# Path to client certificate key
key = /mnt/ramdisk/certificates/mng/client.key

# Path to a secret file that is used to decrypt the client certificate key.
# When using a custom certificate bundle, the 'secretcommand' can instead be 
# used to execute an external command that obtains the secret.
#secretfile = REPLACE_SYNC_SECRET_FILE

###############################################################################
# Log Provider Config
###############################################################################
[log]

# In case that connection to fluent-bit is lost, set how audits/logs are handled
# 
# drop : (default) Protector throws logs away if connection to the fluentbit is lost
# error : Protector returns error without protecting/unprotecting 
# data if connection to the fluentbit is lost
mode = drop

# Host/IP to fluent-bit where audits/logs will be forwarded from the protector
#
# Default localhost
host = localhost
port = 15780

The following table helps you to understand the usage of the parameters listed in the pycore.ini configuration file for DSG.