Privacera Platform master publication

Problem with Trino Server release 379 and above, not with the Privacera plugin (PRIV-11838)

Column-level masking "Partial mask: show last 4" and "Partial mask: show first 4" are not working for the PostgreSQL DB and the Redshift catalog.

The same behaviors have been observed without the Privacera Trino plugin, with the same 'Compiler failed' error, hive working, Redshift not working, and PostgreSQL not working. As a result, the problem appears to be with Trino Server release 379 and above rather than the Privacera plugin.

Request fails when you try to to load users from a large group of users

When trying to load users from a large group of users, the request failed with a 500 Internal server error.

Workaround: To avoid the issue, add the following variables to the config/custom-properties/portal-custom.properties file:

The values are only examples.

hystrix.command.default.execution.isolation.thread.timeoutInMilliseconds=300000
ribbon.ConnectTimeout=60000
ribbon.ReadTimeout=300000
zuul.host.connect-timeout-millis=60000
zuul.host.socket-timeout-millis=300000

"DROP SCHEMA IF EXIST" is not supported in Synapse

Secure Schema is not dropped by Policysync because "DROP SCHEMA IF EXIST" is not supported in Synapse.

Native Row-Level Filter on the table is not working in Synapse

The Native Row-Level Filter on the table is not working in Synapse.

Privacera UserSync for users and groups are no getting updated via LDAP

All users/groups and group membership in Privacera UserSync are not being successfully updated via LDAP.

Workaround: Even if other components are removed, the Privacera UserSync cache may remain. To use the same environment again, the contents of the UserSync cache may need to be manually removed. Use the workdir/usersysnc/rocksdb - rm * command.

Window functions for the table and view is failing for Databricks versions 10.5 and 11.0

For Databricks versions 10.5 and 11.0, if a column attribute is used in a custom udf column masking policy, window functions for the table and view fail.

Solr telemetry errors in Discovery logs for Azure Databricks instances

Solr telemetry errors are observed in Discovery logs for Azure Databricks instances.

Workaround: To stop sending telemetry data to the Solr collection, set the following property in custom.vars file.

DISCOVERY_TELEMETRY_UPDATE_TO_SOLR: "false"

Column-level access policy on public group is not supported in GBQ

In Google BigQuery, creating column level access policy on public group is not supported.

For example, specifying certain column names in an access policy with a public group and then expecting all users to be able to see only values from those columns in secure view is not supported.