Duaer

Integrations

Set up GitHub credentials in Duaer

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

Choose a GitHub credential type

The Duaer GitHub node supports three credentials:

  • GitHub API: create a token under Settings > Developer settings > Personal access tokens in GitHub (for a fine-grained token, pick the repositories and permissions) and put it in Access Token. User is your GitHub user name.
  • GitHub App API: copy App ID (or Client ID) from the app settings, click Generate a private key, and paste the whole PEM file into Private Key. After you install the app on an account or organization, the number at the end of the installation page URL is the Installation ID.
  • GitHub OAuth2 API: create an app under Developer settings > OAuth Apps, set Authorization callback URL to the Duaer OAuth Redirect URL, and put Client ID and Client Secret in the credential.

For GitHub Enterprise Server, change Github Server to your API address, usually https://<host>/api/v3.

GitHub API

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

  • Github Server: The server to connect to. Only has to be set if Github Enterprise is used. Default: https://api.github.com.
  • User
  • Access Token (secret)

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

Duaer nodes that use it: GitHub, Github Trigger.

GitHub App API

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

  • GitHub Server: The server to connect to. Only has to be set if Github Enterprise is used. Default: https://api.github.com.
  • App ID or Client ID (required)
  • Installation ID (required)
  • Private Key (required, secret): PEM private key from the GitHub App.

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

Duaer nodes that use it: GitHub, Github Trigger.

GitHub OAuth2 API

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

  • Client ID (required)
  • Client Secret (required, secret)
  • Github Server: The server to connect to. Only has to be set if Github Enterprise is used. Default: https://api.github.com.

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: repo admin:repo_hook admin:org admin:org_hook gist notifications user write:packages read:packages delete:packages workflow.

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

Save the connection in Duaer

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

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

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

In this section