DSG 4.0.1 is a Tech Preview build intended only for POC/testing environments and must not be used in production environments.
Important:
- Upgrade from DSG 4.0.1 to any future releases is not supported.
- Back up your system before upgrading to DSG 4.0.1.
Configuring the features.json file
Understanding feature flags in the features.json file.
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.
| Configuration | Description | Present by Default |
|---|---|---|
| enhanced-http-transaction-metrics | Enables toggling between legacy and enhanced versions of transaction metrics, with the enhanced version providing more detailed HTTP parameter insights. For more information, refer Transaction Metrics Logging | Yes |
| disable-sftp-client-key-check | In DSG, the SFTP service is designed to enhance security by enforcing strict client public key authentication. This ensures that only valid client keys are accepted during data protection operations. To maintain this high level of security, ensure the disable-sftp-client-key-check parameter is not present in the features.json file, thereby confirming robust verification processes are in place. | Yes |
| normalize-time-labels | When enabled, the normalize-time-labels parameter standardizes default timestamp values. This ensures consistent formatting in transaction metrics logs, which is especially useful for analyzing time-based data. For more information about the normalized time parameter, refer Transaction Metrics Logging. | Yes |
| enhanced-lock-filename | This parameter defines the naming convention for lock files when files are nested within directories in an S3 tunnel. When enabled, it applies a new naming pattern to the generated lock files. For more information about the enhanced-lock-filename parameter, refer Amazon S3 Tunnel. | Yes |
| csv-bytes-parsing | Allows the CSV codec to interpret input as bytes. Useful for preventing Unicode Decode Errors caused by special or nonprintable characters in the data. For more information about the csv-bytes-parsing parameter, refer CSV Payload. | No |
| fw-bytes-parsing | Allows the Fixed Width codec to interpret input as bytes. Useful for preventing Unicode Decode Errors caused by special or nonprintable characters in the data. For more information about the fw-bytes-parsing parameter, refer Fixed Width Payload. | No |
| fw-multi-byte-character | Enables multibyte character support for Fixed Width payload processing in DSG. For more information about the csv-bytes-parsing parameter, refer Fixed Width Payload. | No |
| Configuration | Description | Present by Default |
|---|---|---|
| enhanced-http-transaction-metrics | Enables toggling between legacy and enhanced versions of transaction metrics, with the enhanced version providing more detailed HTTP parameter insights. For more information, refer Transaction Metrics Logging | Yes |
| disable-sftp-client-key-check | In DSG, the SFTP service is designed to enhance security by enforcing strict client public key authentication. This ensures that only valid client keys are accepted during data protection operations. To maintain this high level of security, ensure the disable-sftp-client-key-check parameter is not present in the features.json file, thereby confirming robust verification processes are in place. | Yes |
| normalize-time-labels | When enabled, the normalize-time-labels parameter standardizes default timestamp values. This ensures consistent formatting in transaction metrics logs, which is especially useful for analyzing time-based data. For more information about the normalized time parameter, refer Transaction Metrics Logging. | Yes |
| enhanced-lock-filename | This parameter defines the naming convention for lock files when files are nested within directories in an S3 tunnel. When enabled, it applies a new naming pattern to the generated lock files. For more information about the enhanced-lock-filename parameter, refer Amazon S3 Tunnel. | Yes |
| csv-bytes-parsing | Allows the CSV codec to interpret input as bytes. Useful for preventing Unicode Decode Errors caused by special or nonprintable characters in the data. For more information about the csv-bytes-parsing parameter, refer CSV Payload. | No |
| fw-bytes-parsing | Allows the Fixed Width codec to interpret input as bytes. Useful for preventing Unicode Decode Errors caused by special or nonprintable characters in the data. For more information about the fw-bytes-parsing parameter, refer Fixed Width Payload. | No |
| fw-multi-byte-character | Enables multibyte character support for Fixed Width payload processing in DSG. For more information about the csv-bytes-parsing parameter, refer Fixed Width Payload. | No |
| protegrity-bulk-processing-disabled | Controls whether bulk processing is disabled. When this flag is not present in the features.json file, DSG groups data during extraction based on the payload type. This reduces the number of API calls and improves overall performance. To disable this behavior, add this flag to the features.json file. This flag is supported for the following payloads:
| No |
Adding Feature Flags to the features.json File
- Login to the ESA Web UI.
- Navigate to the Settings > System.
- Go to Cloud Gateway - Settings area, access the features.json file.
- Open the features.json file for editing.
- Add the required feature flags in the features.json file.
Note: Ensure the file is valid JSON after modification.
- Deploy the configurations from the Cluster page on the ESA to apply the changes across all DSGs.
Feedback
Was this page helpful?