Known Issues

Privacera Platform Release 5.0

The following are known issues in the Privacera Platform 5.0 release.

  • PRIV-7328: If inactive for 15 minutes after starting, Glue metastore fails to initialize the cluster.
  • PRIV-7917: Power BI service explorer is not supported.
  • PRIV-7975: Google BigQuery (GBQ): Scanning an invalid resource, such as an incorrect datasource or project identifier, results in a successful scan but with the result shown as "0/0" scanned resources.
  • PRIV-7986: Unicode characters in dictionary content are not properly rendered.
  • PRIV-8060: Scanning is not supported for Presto SQL datasource in Azure.
  • PRIV-8063: Google Cloud Storage (GCS): in Right to Privacy (RTP) policies, the lookup location is not auto-populated and must be added manually.
  • PRIV-8177: In the Expunge policy with a PostgreSQL application, records are not moved to the quarantine table.
  • PRIV-8235: With the Workflow Expunge policy:
    • The file name in the quarantine directory is not same as the original resource file name.
    • A quarantined file should be moved to a subdirectory in the quarentine directory; however, this nested subdirectory structure is erroneously created in the quarantine date directory.
  • PRIV-8326: In the De-identification policy, the original table added in the datazone resource is not deleted. The policy itself functions correctly.
  • PRIV-8378: Create/get encryption schemes fails because port 9292 cannot be accessed.
    • Workaround: On the Privacera host, issue the following commands:
      cd ~/privacera/privacera-manager 
      # Edit the YAML file and add the following line:
      vi config/custom-vars/vars.kubernetes.yml
      RANGER_KMS_EXTERNAL_HTTP_PORT: "9292"
      
      ./privacera-manager.sh update 
      
  • PRIV-8396: After a new installation of Privacera on Docker, at start-up, the Portal displays errors.
    • Workaround: Restart the data server with the following commands:
      cd ~/privacera/privacera-manager
      ./privacera_manager.sh restart dataserver
      
  • PRIV-8454: Spark access control is not supported on Zeppelin Notebook without Livy.
  • PRIV-8455: After upgrading from release 4.7.0.1 to 5.0.0.1.5, the Manage Init Script toggle in Databricks reverts to disabled state.
  • PRIV-8456: Fine-Grained Access Control: Unwanted error messages in Databricks startup logs.
  • PRIV-8457: Fine-Grained Access Control: If a resource path has a space in it, the wrong resource is shown in Ranger Audits.
  • PRIV-8461: Fine-Grained Access Control on Azure: Access control fails for files with special characters in their names.
  • PRIV-8462: Object-Level Access Control, Fine-Grained Access Control: Client IP address is not displayed for R language queries.
  • PRIV-8468: Object-Level Access Control, Fine-Grained Access Control: For Databricks notebooks, email address erroneously recorded in "permission denied" messages, instead of the correct Ranger username.
  • PRIV-8469: Spark Fine-Grained Access Control: Access control via privacera_files for an insert overwrite on the local directory displays extra characters.
  • PRIV-8506: Snowflake advanced audit access history is not working.
  • PRIV-8512: In PolicySync with Synapse, view-based masking and row-level filtering are not working as expected.
  • PRIV-8515: Fine-Grained Access Control: If the username has a full email address, access control does not work properly.
  • PRIV-8544: When JVM security is enabled, the Databricks cluster does not start.
  • PRIV-8548: After Privacera Manager is updated, a running Databricks cluster cannot push audits to Privacera.
    • Workaround: Restart the Databricks cluster.

Last update: August 24, 2021