Table of Contents

Search

  1. Preface
  2. Connectors and Connections
  3. Mass Ingestion connectors
  4. Mass Ingestion connection properties

Connectors and Connections

Connectors and Connections

OAuth 2.0 authorization code authentication

OAuth 2.0 authorization code authentication

The following table describes the Snowflake Data Cloud connection properties for an OAuth 2.0 - AuthorizationCode type connection:
Property
Description
Connection Name
Name of the connection.
Each connection name must be unique within the organization. Connection names can contain alphanumeric characters, spaces, and the following special characters: _ . + -,
Maximum length is 255 characters.
Description
Description of the connection. Maximum length is 4000 characters.
Type
The Snowflake Data Cloud connection type.
Runtime Environment
The name of the runtime environment where you want to run the tasks.
You cannot run application ingestion tasks and database ingestion tasks on a Hosted Agent or serverless runtime environment.
Authentication
The authentication method that Snowflake Data Cloud Connector must use to log in to Snowflake.
Select
AuthorizationCode
.
Account
The name of the Snowflake account.
For example, if the Snowflake URL is https://<123abc>.us-east-2.aws.snowflakecomputing.com/console/login#/, your account name is the first segment in the URL before snowflakecomputing.com. Here, 123abc.us-east-2.aws is your account name.
If you use the Snowsight URL, for example, https://app.snowflake.com/us-east-2.aws/<123abc>/dashboard, your account name is 123abc.us-east-2.aws
Ensure that the account name doesn't contain underscores. To use an alias name, contact Snowflake Customer Support.
Warehouse
The Snowflake warehouse name.
Additional JDBC URL Parameters
The additional JDBC connection parameters.
Enter one or more JDBC connection parameters in the following format:
<param1>=<value>&<param2>=<value>&<param3>=<value>....
For example, pass the database and schema values when you connect to Snowflake:
db=mydb&schema=public
Ensure that there is no space before and after the equal sign (=) when you add the parameters.
Authorization URL
The Snowflake server endpoint that is used to authorize the user request.
The authorization URL is https://<account name>.snowflakecomputing.com/oauth/authorize, where <account name> specifies the full name of your account provided by Snowflake.
For example, https://<abc>.snowflakecomputing.com/oauth/authorize
If the account name contains underscores, use the alias name.
You can also use the Authorization Code grant type that supports the authorization server in a Virtual Private Cloud network.
Access Token URL
The Snowflake access token endpoint that is used to exchange the authorization code for an access token.
The access token URL is https://<account name>.snowflakecomputing.com/oauth/token-request, where <account name> specifies the full name of your account provided by Snowflake.
For example, https://<abc>.snowflakecomputing.com/oauth/token-request
If the account name contains underscores, use the alias name.
Client ID
Client ID of your application generated when you create a security integration of type OAuth in Snowflake.
For more information, see the Snowflake documentation.
Not used by Mass Ingestion application and database ingestion tasks.
Client Secret
Client secret generated for the client ID.
Not used by Mass Ingestion application and database ingestion tasks.
Scope
Determines the access control if the API endpoint has defined custom scopes.
Enter space-separated scope attributes.
For example, specify
session:role:CQA_GCP
as the scope to override the value of the default user role. The value must be one of the roles assigned in Security Integration.
Not used by Mass Ingestion application and database ingestion tasks.
Access Token Parameters
Additional parameters to use with the access token URL.
Define the parameters in the JSON format.
For example, define the following parameters:
[{"Name":"code_verifier","Value":"5PMddu6Zcg6Tc4sbg"}]
Not used by Mass Ingestion application and database ingestion tasks.
Authorization Code Parameters
Additional parameters to use with the authorization token URL.
Define the parameters in the JSON format.
For example, define the following parameters:
[{"Name":"code_challenge","Value":"Ikr-vv52th0UeVRi4"}, {"Name":"code_challenge_method","Value":"S256"}]
Not used by Mass Ingestion application and database ingestion tasks.
Access Token
The access token value.
Enter the populated access token value, or click
Generate Token
to populate the access token value.
Generate Token
Generates the access token and refresh token based on the OAuth attributes you specified.
Refresh Token
The refresh token value.
Enter the populated refresh token value, or click
Generate Token
to populate the refresh token value. If the access token is not valid or expires, the agent fetches a new access token with the help of the refresh token.
If the refresh token expires, provide a valid refresh token or regenerate a new refresh token by clicking
Generate Token
.
Not used by Mass Ingestion application and database ingestion tasks.

0 COMMENTS

We’d like to hear from you!