Integrations
Set up Atlassian credentials in Duaer
Store Atlassian 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 an Atlassian OAuth 2.0 app
The Duaer Atlassian OAuth2 API is the base of Jira SW Cloud OAuth2 API and Confluence Cloud OAuth2 API. Create the app like this:
- In the Atlassian developer console, click Create > OAuth 2.0 integration.
- Under Permissions, add the APIs and scopes you need. Under Authorization, set Callback URL to the Duaer OAuth Redirect URL.
- Copy Client ID and Secret from Settings into the credential. Put space-separated scopes in Scope, including offline_access so the connection renews itself.
For Jira or Confluence, use the matching Jira or Confluence credential, which comes with the scopes preset.
Atlassian OAuth2 API fields in Duaer
In Duaer, choose Atlassian OAuth2 API when you create a credential, then fill in these fields:
- Client ID (required)
- Client Secret (required, secret)
- Scope
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.
Save the connection in Duaer
Open Credentials and create Atlassian. 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.
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 Atlassian secret values appear in Duaer node parameters?
No. In Duaer, Atlassian secrets stay in the credential. Nodes only reference the credential. Execution records should not show the plaintext secret either.
What usually stops a Atlassian 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 Atlassian expects, then confirm you can create credentials in that project.
In this section
Built-in integrations in Duaer
Built-in triggers, actions, and credentials in Duaer. Triggers start a digital organization. Actions run a step after it has started.
IntegrationsRisks of community nodes in Duaer
Before you install a community node in Duaer, know the code comes from a source the instance admin trusts, and know what permissions it gets.
IntegrationsTroubleshoot community nodes in Duaer
When a Duaer community node will not install or run, check the version, permissions, and node docs, then the instance logs.
IntegrationsMake custom API calls for an app in Duaer
When a Duaer app node does not expose the API you need, use HTTP Request and reuse that app’s saved authentication.
IntegrationsIntegrations in Duaer
Built-in triggers, actions, and credentials in Duaer. Community nodes are extra packages. Custom operations reuse saved authentication with HTTP Request.
CredentialsBuilt-in credentials in Duaer
Per-service credential notes for Duaer built-ins. The create flow is in the credentials overview; node docs link to the matching service page.
Create nodesCreate a custom node for Duaer
Write a node package for Duaer when built-in nodes and custom operations are not enough and you will reuse the step.