Updating the Config.ini File

1. Log in to the server as the user with the required permissions.

2. Navigate to the directory where you have downloaded the installation package.

3. To view the contents within the directory, run the following command:

   /opt/protegrity/databaseprotector/teradata/data #  ls -ltr
   

4. Press ENTER.
   The list of available configurable files appears.

   total 4
   -rw-r----- 1 tdatuser tdtrusted 1058 Oct 14 01:27 config.ini
   

5. To open the config.ini file, run the following command:

   /opt/protegrity/databaseprotector/teradata/data # vim config.ini
   

6. Press ENTER.
   The contents of the config.ini file appears.

   ###############################################################################
   # 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
   
   ###############################################################################
   # Protector Config
   ###############################################################################
   [protector]
   
   # cadence is used to decide whether deployment is dynamic or immutable.
   #
   # '0' is used for immutable deployment.
   # Non-negative values other than '0' is used as policy sync interval for dynamic deployment.
   # default cadence value is '60'.
   cadence = 60
   

7. Update the parameters as mentioned in the table.

   The following table consists of the config.ini parameters along with the descriptions:

   Configuration Component	Parameter	Description
   Log	mode	Specifies how the protector logs are handled by the Log Forwarder. If the connection to the Log Forwarder host is lost, you can set the connection mode to one of the following types: - drop: Specifies the logs that the protector fails to record when the connection to the Log Forwarder is lost. By default, the Log Forwarder is configured to operate in the drop mode. - error: Stops all the data security operations and throws an error when the connection to the Log Forwarder is lost. Syntax: Parameter = Value Example: mode = error
   	host	Specifies the Log Forwarder hostname or the IP address where the logs are forwarded from the protector. The default host for the Log Forwarder is localhost. Syntax: Parameter = Value Example: host = <Hostname or IP Address>
   Protector	cadence	Specifies the time interval at which the protector synchronizes with the shared memory for fetching the policy package. The default value for the cadence parameter is 60 seconds. The minimum and maximum values that can be set for the cadence parameter are 0 seconds and 86400 seconds (24 hours) respectively. Important: If the cadence parameter value is set to 0 seconds, then the policy is fetched only once at the time of initialization. After initialization, the protector does not fetch for the new policy changes as a result of immutable deployment. Syntax: Parameter = Value Example: cadence = <time interval in seconds>

8. Save the changes to the config.ini file.

   Important: Restart the Teradata Database to reflect any changes made to the config.ini file.