Duaer

Integrations

Set up Jira credentials in Duaer

Store Jira 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 Jira API token

For Jira Cloud, the simplest option is the Duaer Jira SW Cloud API credential:

  1. Open the Atlassian API tokens page, click Create API token, and copy it.
  2. Put the Atlassian account email in Email, the token in API Token, and the site URL, such as https://your-site.atlassian.net, in Domain.

Jira Server or Data Center: if personal access tokens are available, use Jira SW Server (PAT) API and create one under Personal Access Tokens in your Jira profile. Otherwise use Jira SW Server API with a user name and password.

The token carries all of that account’s Jira permissions. To limit what the workflow can do, use a dedicated account.

Atlassian Service Account

In Duaer, choose Atlassian Service Account when you create a credential, then fill in these fields:

  • Client ID (required): The Client ID of the service account's OAuth 2.0 credential from Atlassian administration.
  • Client Secret (required, secret): The Client Secret of the service account's OAuth 2.0 credential from Atlassian administration.

Note from the dialog: The service account's scopes are chosen when its OAuth 2.0 credential is created in Atlassian administration and can't be changed afterwards. Product permissions still apply on top — grant the service account access to projects and spaces like any other user.

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

Duaer nodes that use it: Confluence, Jira Software.

Jira SW Cloud API

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

  • Email
  • API Token (secret)
  • Domain

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

Duaer nodes that use it: Jira Software, Jira Trigger.

Jira SW Cloud OAuth2 API

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

  • Client ID (required)
  • Client Secret (required, secret)
  • Site URL (required): The URL of your Atlassian site, e.g. https://your-site.atlassian.net. The scheme and any path (like /wiki) are ignored.
  • Custom Scopes: Define custom scopes. Default: off.
  • Enabled Scopes: Scopes that should be enabled. Default: a preset value. Shown when Custom Scopes is on.

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.

By default, Duaer requests these scopes: read:jira-user read:jira-work write:jira-work manage:jira-webhook offline_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: Jira Software, Jira Trigger.

Jira SW Server API

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

  • Email
  • Password (secret)
  • Domain

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

Duaer nodes that use it: Jira Software, Jira Trigger.

Jira SW Server (PAT) API

In Duaer, choose Jira SW Server (PAT) API when you create a credential, then fill in these fields:

  • Personal Access Token (secret)
  • Domain

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

Duaer nodes that use it: Jira Software, Jira Trigger.

Save the connection in Duaer

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

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

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

In this section