Duaer

Integrations

Set up Bitbucket credentials in Duaer

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

Atlassian has retired Bitbucket app passwords, so the Duaer Bitbucket API (App Password) credential can no longer get a working password. Use Bitbucket Access Token API instead:

  1. Open the Atlassian API tokens page, click Create API token with scopes, and pick Bitbucket.
  2. Grant at least read access to the account and repositories, plus webhook read and write. Bitbucket Trigger registers a webhook on the repository or workspace.
  3. Put the Atlassian account email in Email and the token in Access Token.

The webhook Bitbucket Trigger registers must reach Duaer from the internet.

Bitbucket Access Token API

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

  • Email
  • Access Token (secret)

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

Duaer nodes that use it: Bitbucket Trigger.

Bitbucket API

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

  • Username
  • App Password (secret)

Duaer nodes that use it: Bitbucket Trigger.

Save the connection in Duaer

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

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

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

In this section