Duaer

Integrations

Set up GitLab credentials in Duaer

Store GitLab 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 GitLab access token

The Duaer GitLab API credential:

  1. In GitLab, open User Settings > Access tokens and create a personal access token with the api scope (read_api for read-only), and set an expiry date.
  2. Copy the token into Access Token.
  3. For self-managed GitLab, change Gitlab Server to your address, such as https://gitlab.example.com.

For the GitLab OAuth2 API type, create an application under User Settings > Applications, set Redirect URI to the Duaer OAuth Redirect URL, and put Application ID and Secret into Client ID and Client Secret.

GitLab API

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

  • Gitlab Server: Default: https://gitlab.com.
  • Access Token (secret)

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

Duaer nodes that use it: GitLab, GitLab Trigger.

GitLab OAuth2 API

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

  • Client ID (required)
  • Client Secret (required, secret)
  • Gitlab Server: Default: https://gitlab.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: api.

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

Save the connection in Duaer

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

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

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

In this section