Skip to content

Known Issues, Privacera Platform 4.7

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

PolicySync and Discovery: Snowflake JDBC Connection String

This issue affect PolicySync and Discovery.

The Snowflake JDBC connection string needs to include the parameter application=privacera to indicate that the application involved is Privacera.

The syntax depends on whether your JDBC connection already has parameters or not.

Double-check the examples here against your own actual connection strings.

  • If the connection string does not have any parameters, append ?application=privacera ias a query string to the original connection string, as shown below:

    • Original: jdbc:snowflake://xy12345.us-east.aws.snowflakecomputing.com
    • New: jdbc:snowflake://xy12345.us-east1.aws.snowflakecomputing.com?application=privacera

  • If the connection string already has parameters, append &application=privacera as an argument to the query string, as shown below:

    • Original: jdbc:snowflake://xy12345.snowflakecomputing.com?warehouse=mywh
    • New: jdbc:snowflake://xy12345.snowflakecomputing.com?warehouse=mywh&application=privacera