Duaer

Integrations

Set up HTTP Request credentials in Duaer

Store HTTP Request 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.

Pick an HTTP Request credential type

When the Duaer HTTP Request node uses Generic Credential Type, pick the credential that matches the auth the API docs ask for:

  • Key in a header, such as X-API-Key: Header Auth. Key in Authorization: Bearer: Bearer Auth.
  • Key in a query parameter, such as ?api_key=: Query Auth.
  • User name and password: Basic Auth or Digest Auth.
  • Several headers at once: Multiple Headers Auth. A mix of headers, body, and query: Custom Auth, with headers, body, and qs in JSON.
  • OAuth: OAuth2 API or OAuth1 API. Mutual TLS: SSL Certificates.
{
  "headers": { "X-API-Key": "<your key>" },
  "qs": { "appid": "<your app id>" }
}

When the API belongs to an app that already has a Duaer node, choose Predefined Credential Type instead and reuse that app’s credential. Refer to custom operations.

Basic Auth

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

  • User
  • Password (secret)

Duaer nodes that use it: Duaer Form Trigger, GraphQL, HTTP Request, Pipedrive Trigger, Wait, Webhook.

Bearer Auth

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

  • Bearer Token (secret)

Note from the dialog: This credential uses the "Authorization" header. To use a custom header, use a "Header Auth" credential instead.

Digest Auth

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

  • User
  • Password (secret)

Duaer nodes that use it: GraphQL, HTTP Request.

Header Auth

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

  • Name
  • Value (secret)

Note from the dialog: To send multiple headers, use a "Custom Auth" credential instead.

Duaer nodes that use it: GraphQL, HTTP Request, Wait, Webhook.

Multiple Headers Auth

In Duaer, choose Multiple Headers Auth when you create a credential, then fill in these fields:

  • Headers

Custom Auth

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

  • JSON (required): Use json to specify authentication values for headers, body and qs.

Duaer nodes that use it: GraphQL.

Query Auth

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

  • Name
  • Value (secret)

Duaer nodes that use it: GraphQL, HTTP Request, Jira Trigger.

SSL Certificates

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

  • CA (secret): Certificate Authority certificate.
  • Certificate (secret)
  • Private Key (secret)
  • Passphrase (secret): Optional passphrase for the private key, if the private key is encrypted.

Duaer nodes that use it: HTTP Request.

OAuth1 API

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

  • Authorization URL (required)
  • Access Token URL (required)
  • Consumer Key (required, secret)
  • Consumer Secret (required, secret)
  • Request Token URL (required)
  • Signature Method (required): Default: HMAC-SHA1. Options: HMAC-SHA1, HMAC-SHA256, HMAC-SHA512.

Register the OAuth Redirect URL that the Duaer credential dialog shows (https://<your-duaer-host>/rest/oauth1-credential/callback) with the provider, then click Connect my account in Duaer.

Duaer nodes that use it: GraphQL, HTTP Request.

OAuth2 API

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

  • Grant Type: Default: Authorization Code. Options: Authorization Code, Client Credentials, PKCE.
  • Authorization URL (required): Shown when Grant Type is Authorization Code or PKCE.
  • Access Token URL (required)
  • Client ID (required)
  • Client Secret (required, secret)
  • Scope
  • Auth URI Query Parameters: For some services additional query parameters have to be set which can be defined here. Shown when Grant Type is Authorization Code or PKCE.
  • Authentication: Default: Header. Options: Body, Header.
  • Send Additional Body Properties: Default: off. Shown when Grant Type is Client Credentials.
  • Additional Body Properties: Shown when Grant Type is Client Credentials.
  • Ignore SSL Issues (Insecure): Default: off.
  • Token Expired Status Code: HTTP status code that indicates the token has expired. Some APIs return 403 instead of 401. Default: 401.
  • Encrypted Tokens (JWE): Whether the IdP returns tokens encrypted as JWE to the public key at this instance’s JWKS endpoint. The response must contain at least one JWE-encrypted token (access or ID token); fully plaintext responses are rejected. Default: off.
  • JWKS URI: Provide this URL to your IdP so it can fetch the public key used to encrypt access and ID tokens for this instance. Shown when Encrypted Tokens (JWE) 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.

Duaer nodes that use it: GraphQL, HTTP Request.

Save the connection in Duaer

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

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

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

In this section