4 Connect to Data for Pixel-Perfect Reports

This topic describes how to connect to data sources for creating pixel-perfect reports using Publisher.

Set Up Key-pair Authentication to Snowflake Data Warehouse

Connect Analytics Publisher to Snowflake Data Warehouse using key-pair authentication.

Before you begin:
  • • Generate a Snowflake public/private key pair and retain the private key securely.
  • • Add the public key to the target Snowflake user before configuring Publisher.
  • • Have the Snowflake JDBC connection string and service-user name ready.
  • • Use a Publisher administrator account with access to Upload Center and JDBC data sources.
  1. Prepare the Snowflake key pair.
    Generate the public/private key pair according to your Snowflake security process. Register the public key on the intended Snowflake user. Only the private key is uploaded to Oracle Analytics Publisher.
    Security requirement: Do not paste the private-key contents into the JDBC form or include the private key in documentation. Restrict access to the source key and rotate it under your normal credential-rotation policy.
  2. Upload the private key to Publisher.
    In Publisher, navigate to Administration > Upload Center.
    • Choose Browse and select the private-key file.
    • Set File Type to SSH Private Key.
    • Select Upload. Use Overwrite only when replacing an existing file with the same name.
    • Confirm that the uploaded key appears under Manage Uploaded Files.
  3. Create or edit the Snowflake JDBC data source.
    • Driver Type - specify Snowflake.
    • Database Driver Class - specify net.snowflake.client.jdbc.SnowflakeDriver.
    • Connection String - use the Snowflake JDBC format:
      jdbc:snowflake://<account>.snowflakecomputing.com;db=<database>;warehouse=<warehouse>;schema=<schema>;
    • Username - specify the Snowflake service-user login name.
    • Password - specify the private-key passphrase only if the uploaded private key is encrypted; otherwise leave it blank.
    • SSH Private Key - select the private key uploaded in Upload Center.
  4. Select the uploaded key and test.
    In the SSH Private Key list, choose the private key uploaded in the previous step. The driver is Snowflake, and the Test Connection control is available directly beneath the key selection.
    • • If the private key is encrypted, enter its passphrase in the Password field; otherwise leave the field blank.
    • • Select Test Connection and verify that it succeeds.
    • • Select Apply to save the working configuration.

    Note:

    For key-pair authentication, the Password field is used for the private-key passphrase when one is required. It is not a place to store the Snowflake account password.
  5. Set access to the data source.
    Define the security roles that can create or view reports using this data source. Limit access to the roles that require it, consistent with your Publisher security model.
  6. Validate use in Publisher.
    Create or open a Publisher data model that uses the Snowflake JDBC data source.
    Run a sample data set and confirm that it returns rows.
    If bursting uses the data source, run a controlled burst and confirm successful delivery.
Troubleshooting
  • Private key is not listed - Verify that the file was uploaded in Upload Center with File Type set to SSH Private Key. Refresh the data-source page after the upload.
  • Authentication fails - Confirm that the public key registered on the Snowflake user matches the uploaded private key and that the correct Snowflake username is supplied.
  • Encrypted key fails - Re-enter the private-key passphrase in the Password field. Leave the field blank only for an unencrypted private key.
  • Connection test fails - Validate the Snowflake JDBC URL, account/network reachability from the OAC environment, warehouse/database/schema access, and Snowflake user permissions.