January 2026
The Continuous Compliance 2026.1.0.0 release centralizes LDAP configuration for Continuous Compliance engines by moving all configuration to the setup application and applying it at engine startup. It also adds support for Salesforce metadata management tasks via proxy, enabling proxy-based operations through automatically detected JDBC parameters.
New features
LDAP configuration centralization
Starting in 2026.1, LDAP configuration for Continuous Compliance engines is managed exclusively through the setup application and applied at engine startup. LDAP settings are no longer visible or configurable via the Continuous Compliance UI or API. Containerized deployments are unaffected, and DCT is not impacted.
GCP Shielded VM integrity reset required after upgrade
Engine upgrades that introduce new kernel or bootloader components may trigger integrity alerts on GCP Shielded VMs with vTPM and IMA enabled. After the upgrade, run the integrity reset command to establish the updated boot measurements as the trusted baseline. For more information and the required command, see the Reset integrity boot measurements for GCP Shielded VM section.
Support for Salesforce metadata management tasks via proxy
Release version 2025.2.0 for DXRT provides new proxy options to support metadata management operations (as specified here) on Salesforce connectors via a proxy. These options have now been integrated with continuous compliance. The proxy details will automatically be identified from the jdbc url parameters (ProxyServer and ProxyPort) used to connect to Salesforce via proxy as specified by https://cdn.cdata.com/help/RFJ/jdbc/RSBSalesforce_c_Proxy.htm.
Fixed issues
| Bug number | Description |
|---|---|
| DLPX-76402 | Fixed an issue where SSO logins to Masking could fail with an HTTP 500 error due to case-sensitive username mismatches between audit records and Masking users. |
| DLPX-95406 | Fixed a missing file error during deletion of imported DB2 dataset formats. |
| DLPX-95651 | Fixed an issue by normalizing legacy environment purpose values during upgrade to prevent failures caused by invalid data. |
| DLPX-95689 | Fixed an error when creating identity columns in MSSQL tables with quotation marks in the table name. |
| DLPX-95790 | Fixed an issue where Masking, Tokenization, or Re-identification jobs failed when the prefix was empty for cloud connectors. |
| DLPX-96023 | Fixed an issue where jobs associated with Parquet file types were not syncable. |
| DLPX-96175 | Fixed an edge case in Parquet file masking where dictionary-encoded columns with many null values could impact row alignment, potentially leading to incorrect values being written across rows and loss of referential integrity. |
Known issues
|
Key |
Summary |
Workaround |
|---|---|---|
| DLPX-80640 | Masking drop Indexes task does not find and remove indexes on SQL Server partitioned tables in both on-the-fly and in-place masking jobs. | Manually script the drop and recreate indexes. |
| DLPX-81694 | When masking two columns with the same name but different casing, the same algorithm may be incorrectly applied to both. | None |
| DLPX-93701 | On the fly masking job fails when using different source and target connector types (mixed Cloud and On-premise connectors) for JSON, XML, and Parquet files. | None |
| DLPX-95510 | Parquet masking jobs fail in GCP interoperability mode when the GCP bucket name contains underscores. This occurs because the Hadoop S3A client enforces AWS bucket-naming rules before the request reaches GCS. | None |