Duaer

Integrations

Set up MySQL credentials in Duaer

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

Connect to your MySQL database

The Duaer MySQL credential connects from the Duaer server:

  • Host: a host name or IP the Duaer server can reach. When Duaer runs in Docker, do not use localhost; use the database service name or the host address.
  • Port defaults to 3306. Fill in Database, User, and Password. The database user must be allowed to sign in from the host Duaer runs on.
  • When the database requires TLS, turn on SSL and fill in CA Certificate, Client Certificate, and Client Private Key as needed.
  • When the database is reachable only through a bastion host, turn on SSH Tunnel.

When the connection fails, refer to MySQL common issues.

MySQL fields in Duaer

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

  • Host: Default: localhost.
  • Database: Default: mysql.
  • User: Default: mysql.
  • Password (secret)
  • Port: Default: 3306.
  • Connect Timeout: The milliseconds before a timeout occurs during the initial connection to the MySQL server. Default: 10000.
  • SSL: Default: off.
  • CA Certificate (secret): Shown when SSL is on.
  • Client Private Key (secret): Shown when SSL is on.
  • Client Certificate (secret): Shown when SSL is on.
  • SSH Tunnel: Default: off.
  • SSH Authenticate with: Default: Password. Options: Password, Private Key. Shown when SSH Tunnel is on.
  • SSH Host: Default: localhost. Shown when SSH Tunnel is on.
  • SSH Port: Default: 22. Shown when SSH Tunnel is on.
  • SSH User: Default: root. Shown when SSH Tunnel is on.
  • SSH Password (secret): Shown when SSH Tunnel is on.
  • Private Key (secret): Shown when SSH Tunnel is on.
  • Passphrase: Passphrase used to create the key, if no passphrase was used leave empty. Shown when SSH Tunnel is on.

Duaer nodes that use it: MySQL.

Save the connection in Duaer

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

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

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

In this section