Duaer

Integrations

Set up MongoDB credentials in Duaer

Store MongoDB 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 MongoDB

The Duaer MongoDB credential has two modes, set by Configuration Type:

  • Connection String: easiest with MongoDB Atlas. In Atlas, open Connect > Drivers, copy the mongodb+srv:// string, replace <password> with the database user’s password, and paste it into Connection String.
  • Values: for a self-hosted MongoDB, fill in Host, Port (default 27017), User, and Password.
  • Both modes need Database. The credential dialog notes that Database is still required with a connection string.

With Atlas, add the Duaer server’s outbound IP to the Network Access IP list, or connections time out. When the database requires TLS, turn on TLS and add certificates as needed.

MongoDB fields in Duaer

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

  • Configuration Type: Default: Values. Options: Connection String, Values.
  • Connection String (secret): If provided, the value here will be used as a MongoDB connection string, and the MongoDB credentials will be ignored. Shown when Configuration Type is Connection String.
  • Host: Default: localhost. Shown when Configuration Type is Values.
  • Database: Note: the database should still be provided even if using an override connection string.
  • User: Shown when Configuration Type is Values.
  • Password (secret): Shown when Configuration Type is Values.
  • Port: Default: 27017. Shown when Configuration Type is Values.
  • Use TLS: Default: off.
  • CA Certificate (secret): Shown when Use TLS is on.
  • Public Client Certificate (secret): Shown when Use TLS is on.
  • Private Client Key (secret): Shown when Use TLS is on.
  • Passphrase (secret): Shown when Use TLS is on.

Duaer nodes that use it: MongoDB.

Save the connection in Duaer

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

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

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

In this section