Security and Authentication

To protect data from unauthorized access, BigQuery data stores require all connections to be authenticated using the OAuth 2.0 protocol. The Simba Google BigQuery JDBC Connector provides mechanisms that allow you to complete an OAuth 2.0 authentication flow using a personal Google account, a Google service account, or Application Default Credentials. You can also specify an access token or refresh token that you have already generated from the Google Authorization Server, and use those credentials to connect to Google BigQuery.

When you connect to BigQuery using a personal Google account, a Google service account, or Application Default Credentials, the connector automatically initiates an OAuth 2.0 authentication flow. The connector retrieves an access token based on the credentials specified in the connection URL, and then uses the token to authenticate the connection to the database. When you connect using an access token or refresh token, the connector authenticates the connection to BigQuery without going through an OAuth 2.0 authentication flow.

For detailed connector configuration instructions, see Configuring Authentication.

For more information about OAuth 2.0, see "Using OAuth 2.0 to Access Google APIs" in the Google Identity Platform documentation: https://developers.google.com/identity/protocols/OAuth2.

Related topics

• Configuring Authentication
• Authentication Driver Configuration Options
• Features
• Installing and Using the Simba Google BigQuery JDBC Connector
• Configuring the Simba Google BigQuery JDBC Connector
• Connector Configuration Options