Duaer

Integrations

Set up Snowflake credentials in Duaer

Store Snowflake connection details in Duaer for digital-organization nodes to use at runtime. Secrets are protected by the instance encryption key and are not written into node parameters.

Connect to Snowflake

For the Duaer Snowflake credential, prefer Key-Pair authentication. Snowflake is phasing out password-only sign-in:

  1. Generate a key: openssl genrsa 2048 | openssl pkcs8 -topk8 -nocrypt -out rsa_key.p8, then export the public key with openssl rsa -in rsa_key.p8 -pubout.
  2. In Snowflake, run ALTER USER <user> SET RSA_PUBLIC_KEY='<public key>'.
  3. In the Duaer credential, set Authentication to Key-Pair, fill in Username, and paste the whole rsa_key.p8 file into Private Key. Fill in Passphrase if the key is encrypted.
  4. Account is the account identifier: the part before .snowflakecomputing.com in the account URL, such as myorg-myaccount. Warehouse is needed to run queries; fill in Database, Schema, and Role as needed.

For Snowflake OAuth2 API, first create an OAuth integration in Snowflake with CREATE SECURITY INTEGRATION and set OAUTH_REDIRECT_URI to the Duaer OAuth Redirect URL. The default scopes sign in with the SYSADMIN role.

Snowflake

In Duaer, choose Snowflake when you create a credential, then fill in these fields:

  • Account: Enter the name of your Snowflake account.
  • Database: Specify the database you want to use after creating the connection.
  • Warehouse: The default virtual warehouse to use for the session after connecting. Used for performing queries, loading data, etc.
  • Authentication: The way to authenticate with Snowflake. Default: Password. Options: Password, Key-Pair.
  • Username
  • Password (secret): Shown when Authentication is Password.
  • Private Key (required, secret): Private PEM key for Key-pair authentication with Snowflake, follow guide here (https://docs.snowflake.com/en/user-guide/key-pair-auth) Shown when Authentication is Key-Pair.
  • Passphrase (secret): If the private key is encrypted, you must provide the passphrase used to encrypt it.
  • Schema: Enter the schema you want to use after creating the connection.
  • Role: Enter the security role you want to use after creating the connection.
  • Origin Hostname: Optional Snowflake hostname to use for the connection.
  • Client Session Keep Alive: Whether to keep alive the client session. By default, client connections typically time out approximately 3-4 hours after the most recent query was executed. If the parameter clientSessionKeepAlive is set to true, the client’s connection to the server will be kept alive indefinitely, even if no queries are executed. Default: off.

Duaer nodes that use it: Snowflake.

Snowflake OAuth2 API

In Duaer, choose Snowflake OAuth2 API when you create a credential, then fill in these fields:

  • Client ID (required)
  • Client Secret (required, secret)
  • Account (required): Your Snowflake account identifier (e.g. xy12345 or xy12345.us-east-1). Used to construct the OAuth2 authorization and token URLs.
  • Database: Specify the database you want to use after creating the connection.
  • Warehouse: The default virtual warehouse to use for the session after connecting. Used for performing queries, loading data, etc.
  • Schema: Enter the schema you want to use after creating the connection.
  • Client Session Keep Alive: Whether to keep alive the client session. By default, client connections typically time out approximately 3-4 hours after the most recent query was executed. If the parameter clientSessionKeepAlive is set to true, the client's connection to the server will be kept alive indefinitely, even if no queries are executed. Default: off.
  • Custom Scopes: Define custom scopes. Default: off.
  • Enabled Scopes: Scopes that should be enabled. Default: refresh_token session:role:SYSADMIN. Shown when Custom Scopes is on.

Duaer uses the OAuth2 PKCE grant for this type.

In the provider’s app settings, register the OAuth Redirect URL that the Duaer credential dialog shows (https://<your-duaer-host>/rest/oauth2-credential/callback). Then click Connect my account in Duaer and approve access.

By default, Duaer requests these scopes: refresh_token session:role:SYSADMIN.

Optional settings shared by every Duaer OAuth2 credential: Ignore SSL Issues (Insecure), Token Expired Status Code, Encrypted Tokens (JWE), JWKS URI. They are described under OAuth2 API.

Duaer nodes that use it: Snowflake.

Save the connection in Duaer

Open Credentials and create Snowflake. Fill in the key, OAuth, or server fields. After you save, digital-organization nodes reference this credential instead of putting the secret in a parameter.

Credential values are protected by the instance encryption key. If you change or lose that key, stored credentials cannot be decrypted. See the hosting notes on encryption keys. The matching node is under the related node.

Who can use this credential

Who can see or edit it follows projects and roles. Do not paste secrets into chat or variables. External vaults are covered under external secrets.

Questions

Do Snowflake secret values appear in Duaer node parameters?

No. In Duaer, Snowflake secrets stay in the credential. Nodes only reference the credential. Execution records should not show the plaintext secret either.

What usually stops a Snowflake credential from saving in Duaer?

Wrong fields, an OAuth callback that does not match the instance URL, or a role that cannot create credentials. Check the fields Snowflake expects, then confirm you can create credentials in that project.

In this section