Duaer

Integrations

Set up Box credentials in Duaer

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

Create a Box app

The Duaer Box OAuth2 API credential:

  1. In the Box Developer Console, click Create New App > Custom App and choose User Authentication (OAuth 2.0).
  2. Under Configuration, add the Duaer OAuth Redirect URL to Redirect URIs and tick read and write for files under Application Scopes. For Box Trigger, also tick Manage webhooks.
  3. Put Client ID and Client Secret in the credential and click Connect my account.

Primary Signature Key and Secondary Signature Key are optional and verify webhooks Box sends. Generate them under Manage signature keys on the app’s Webhooks tab; fill in both while rotating keys.

Box OAuth2 API fields in Duaer

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

  • Client ID (required)
  • Client Secret (required, secret)
  • Primary Signature Key (secret): Used to verify the authenticity of webhook requests. Find it in the Box Developer Console under your app's Webhooks tab > Manage signature keys.
  • Secondary Signature Key (secret): Used to verify the authenticity of webhook requests during key rotation. Find it in the Box Developer Console under your app's Webhooks tab > Manage signature keys.

Duaer uses the OAuth2 Authorization Code 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.

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: Box, Box Trigger.

Save the connection in Duaer

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

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

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

In this section