Fixed an issue that blocked logins using Duo SSO.
Fixed an issue that caused sensitivity scans to fail on workspaces that contained document columns and where Tonic Table Parallelism was set to 2 or above.
On the workspace settings page, replaced the Block Data Generation on Schema Changes toggle with a set of options. The new options are Do Not Block, Block On Sensitive Changes, and Block On All Changes.
Structural now correctly preserves the original value for columns that contain constant values and that are assigned the Continuous generator. A previous fix addressed this partially, but some edge cases still caused the original value to be lost or triggered an error during generation. This is now fully resolved.
SQL Server - Fixed a performance regression when masking tables that have large row volumes.
Fixed an issue where when the Character Substitution generator was applied to a primary key column in a subsetting target table, data generation failed.
Fixed a regression introduced in v1459 where workspaces that used a secrets manager for password retrieval did not load if an error occurred during the secret retrieval.
Upsert - Changed the upsert pre-job check to no longer fail when the destination database is missing tables that exist in the source.
SQL Server - Fixed a performance regression when masking tables that have large row volumes.
Oracle: Tonic Structural now bases the list of required privileges and catalog packages on the features in use in the source database. The privilege check performed at the start of a generation job now gives an error instead of a warning if privileges are missing.
PostgreSQL - Fixed an issue issue where connection pool limits were not always being respected when creating PostgreSQL connection strings.
Fixed an issue where setting query filter on a non-target subsetting table caused errors.
The Structural API now provides an api/Privacy/history/search endpoint to allow you to issue paginated queries of privacy events. These are the same events that display on the Protection Audit Trail on Privacy Hub.
Revised schema change type definition and handling - We have changed how we categorize and respond to detected schema changes.
Sensitive schema changes include schema changes that could result in data leakage. These include new tables and columns, new collections and path types, changes to column data types, and changes to nullability. These types of schema changes always block data generation. Schema Changes view includes options to resolve these changes.
Notifications are schema changes that Structural resolves automatically for each data generation, unless the workspace is configured to block data generation for all schema changes. Notifications include removed tables and columns, removed collections and paths, and changing a column to a foreign key. To permanently resolve these changes, you address them on Schema Changes view.
Fixed an issue where in specific cases when tables had 4 or fewer rows, columns that contained credit card numbers were sometimes not identified as containing sensitive data.