Skip to main content

User Guide

Access Data

As a data consumer, you can access data external to the Privitar Data Security Platform​ through a query from a SQL query or business intelligence (BI) tool using a custom connection.

Important

Only an exchange administrator, the data consumer who created the consumption project, or a member of the project may access the data in that project.

Make sure that you have a copy of the supported data proxy JDBC driver installed in your SQL query or business intelligence (BI) tool for the version of the Privitar Data Security Platform​ that you are using.

  1. Click Projects in the left navigation.

  2. Click the title of a project on the Published tab.

  3. Click the Assets and Access tab.

  4. Click Copy Proxy URL to copy the address of the proxy to your computer's clipboard.

  5. Launch your SQL query or business intelligence (BI) tool of choice.

    Examples of SQL query tools include Microsoft SQL Server, dbForge, and RazorSQL. Examples of BI tools include Tableau® and SAS® Visual Analytics.

  6. Refer to your SQL query or BI tool's documentation for creating a custom data driver for connecting to data. You will need to supply the following information:

    1. The path to the location of the data driver.

    2. Your Privitar Data Security Platform​ user credentials (the username and password that you use to log in to the platform).

    3. The driver class name, which is: com.privitar.dataplane.integrations.dynamic.jdbc.DataProxyDriver

    4. The proxy URL that you copied in the previous steps.

    Ensure that when creating the custom data connection, the parameter's TLS (sometimes called "SSL") flag is set to True in your tool.

  7. Using the supplied data proxy driver, use the proxy URL to connect to the data assets in the project and to retrieve de-identified data based on the policies and rules defined on the platform.

Note

If there is an error when authenticating a connection, the error message may not contain enough information to indicate the exact cause of the problem. Please validate the connection URL, credentials, and TrustStore certificate are correct.

Note

Some data source drivers don't provide a default schema. For these, you need to fully qualify your table (schema.table) in order to query it.

In this section: