Duaer

Integrations

Set up Databricks credentials in Duaer

Store Databricks 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.

Databricks

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

  • Host (required): Domain of your Databricks workspace.
  • Personal Access Token (required, secret): Databricks personal access token.

When you save, Duaer tests the connection with these values.

Duaer nodes that use it: Databricks, Databricks Trigger.

Databricks OAuth2 API

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

  • Grant Type: Default: Client Credentials (Service Principal). Options: Client Credentials (Service Principal), Authorization Code (User).
  • Client ID (required)
  • Client Secret (required, secret)
  • Host (required): Domain of your Databricks workspace, must be https.
  • Custom Scopes: Whether to define custom OAuth scopes instead of the default all-apis. Default: off.
  • Enabled Scopes: Space-separated OAuth scopes to request. Default: all-apis. Shown when Custom Scopes is on.
  • Enabled Scopes: Space-separated OAuth scopes to request. Default: all-apis offline_access. Shown when Custom Scopes is on.

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: :.

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

When you save, Duaer tests the connection with these values.

Duaer nodes that use it: Databricks, Databricks Trigger.

Save the connection in Duaer

Open Credentials and create Databricks. 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 Databricks secret values appear in Duaer node parameters?

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

What usually stops a Databricks 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 Databricks expects, then confirm you can create credentials in that project.

In this section