Versions Compared

Old Version 33

changes.mady.by.user Kalpana Malladi

Saved on

compared with

New Version 34

changes.mady.by.user Cindy Hall

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Table of Contents
minLevel1
maxLevel2
absoluteUrltrue

Overview

You can use this account Use this SnapLogic Account type to connect Snaps to Google BigQuery Snaps with data sources that use the Google Service using a Google service account.

Prerequisites

  • Existing Google Service Account with P12 file containing the private key. Learn how to import P12 File into the Google Service Account.

  • JDK with Keytool utility to set up the Keystore. 

Limitations and Known Issues

None.

Account Settings

...

Info

  • Asterisk ( * ): Indicates a mandatory field.

  • Suggestion icon ( (blue star) ): Indicates a list that is dynamically populated based on the configuration.

  • Expression icon ( (blue star) ): Indicates the value is an expression (if enabled) or a static value (if disabled). Learn more about Using Expressions in SnapLogic.

  • Add icon ( (blue star) ): Indicates that you can add fields in the field set.

  • Remove icon ( (blue star) ): Indicates that you can remove fields from the field set.

Field Name

Field Type

Description

Label*

Default Value: None
Example: Service Account

String/Expression

Specify a unique label for the account.

Properties for Google BigQuery

Account ID*   

Default Value: None
Example: 108275755

Integer/Expression

Specify the ID of the service account available in the Google web console.

Private Key ID* 

Default Value: N/A
Example: 4fb718fd54de73f0

String/Expression

Specify the ID of the private key available in the Google web console.

Email ID*

Default Value: N/A
Example: test1@0.iam.gserviceaccount.com

String/Expression

Specify the email id of the service account available in the Google web console.

Keystore URI*

Default Value: N/A
Example: g_bigq

String/Expression

Specify the location of the Keystore that contains the private key you use. You can upload the file using the Upload icon.

Keystore Passphrase*

String/Expression

Specify the passphrase to access the Keystore.

Private Key Alias*

Default Value: N/A
Example: privatekey

String/Expression

Specify the alias to identify the private key. This is a suggestible field and will lists all the available aliases in the key store.

Properties for Cloud Storage

Account ID 

Default Value: N/A
Example: 108275755

Integer/Expression

Specify the ID of the service account available in the Google web console.

Private Key ID 

Default Value: N/A
Example: 4fb718fd54de73f0

String/Expression

Specify the ID of the private key available in the Google web console.

Email ID 

Default Value: None
Example: test1@0.iam.gserviceaccount.com

String/Expression

Specify the email id of the the service account available in the Google web console.

Keystore URI

Default Value: N/A
Example: test/g_bigquery

String/Expression

Specify the location of the Keystore that contains the private key to be used. Click the browse icon to load into/select from SLDB.

Keystore Passphrase

Default Value: N/A
Example: Encrypted value

String/Expression

Specify the passphrase to access the Keystore.

Private Key Alias 

Default Value: N/A
Example: privatekey

String/Expression

Specify the alias to identify the private key. This is a suggestible field and will list all the aliases in the key store.

Default Standard SQL

Default Value: Deselected

Checkbox

Select this checkbox if you want to default the dialect in the Query field in the Snaps using this account to Standard SQL.

Info

To override this default setting use the #legacySQL tag within the Query field of the Snap to treat it as a Legacy SQL query.

...

Importing P12 File
Anchor
Importing-P12-File
Importing-P12-File

Key Steps

  1. Create a new Keystore.

  2. Empty the Keystore.

  3. Verify if the Keystore is empty.

  4. Import the P12 file.

  5. Check the Keystore is non-empty.

  6. Change the alias, if needed.

  7. Verify a new alias.

To perform the above steps, open a Command Prompt window. The steps along with the requisite syntax are described in detail below:

Anchor
Step-1
Step-1

Step 1 - Create New Keystore

  1.  Execute the following command at the Command Prompt.
    keytool -genkey -alias <some alias> -keyalg RSA -keysize 2048 -keystore <keystore name> Example: keytool -genkey -alias demoalias1 -keyalg RSA -keysize 2048 -keystore demokeystore1

  2. Specify the follow-up questions for First and Last name, Organizational unit name, Organization name, City/Locality, State/Province, and Two-letter country code.

  3. Click Yes in the Details confirmation dialog box.

  4. Enter the key password for the provided alias.

  5. Press Enter.

Note

The same key password will be used in the subsequent steps.

Anchor
Step-2
Step-2

Step 2 - Empty the Keystore

  1. Execute the following command at the Command Prompt:
    keytool -delete -alias <alias name> -keystore <keystore name> Example: keytool -delete -alias demoalias1 -keystore demokeystore1

  2. Enter the password as given in Step 1.

Anchor
Step-3
Step-3

Step 3 - Verify if Keystore is Empty

  1. Execute the following command at the Command Prompt:
    keytool -v -list -keystore <keystre name> Example: keytool -v -list -keystore demokeystore1

  2. Enter password as given in Step 1.
    The response should be "Your keystore contains 0 entries".

Anchor
Step-4
Step-4

Step 4 - Import the P12 file

  1. Execute the following command at the Command Prompt:
    keytool -v -importkeystore -srckeystore <p12file.p12> -srcstoretype PKCS12 -destkeystore <keystore name> -deststoretype JKS -destkeypass <password for private key (should be same as keystore passphrase)> Example: keytool -v -importkeystore -srckeystore sample_p12_file.p12 -srcstoretype PKCS12 -destkeystore demokeystore1 -deststoretype JKS -destkeypass demoPassword1

  2. Enter the destination Keystore password given in Step 1.

  3. Enter the source Keystore password that was obtained while generating P12 file.

The response should be "Import command completed: 1 entries successfully imported, 0 entries failed or canceled".

Anchor
Step-5
Step-5

Step 5 - Check Keystore to be Non-empty

  1. Execute the following command at the Command Prompt:

    Code Block
    keytool -v -list -keystore <keystre name>
Example: 
keytool -v -list -keystore demokeystore1

  2. Enter password as given in Step 1. The response should show:

...

Info

Steps 6 & 7 are needed if you want to change the alias for the imported private key.

Anchor
Step-6
Step-6

Step 6 - Change Alias if needed

  • Execute the following command at the Command Prompt:

Code Block
keytool -changealias -keystore <keystore name> -alias <current alias> -destalias <new alias>
Example: 
keytool -changealias -keystore demokeystore1 -alias privatekey -destalias first_entry

The response will be blank if the change is successful.

Anchor
Step-7
Step-7

Step 7 - Verify New Alias

Repeat Step 5 and ensure the alias name is what is given in Step 6. The Keystore "demokeystore1" is ready to be used in the snaps with the passphrase given in Step 1.

...

Insert excerpt
Google BigQuery Snap Pack
Google BigQuery Snap Pack
nameGoogle BigQuery SPH
nopaneltrue

...

Related Content