Duaer

Integrations

Set up TimescaleDB credentials in Duaer

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

Fill in the Duaer TimescaleDB credential as you would for Postgres:

  • Host, Port, Database, User, and Password come from the service’s connection details. Timescale Cloud shows them under Connection info; the port is not always 5432.
  • SSL defaults to Disable. Timescale Cloud and most managed databases require encryption, so set it to Require.
  • When Duaer runs in Docker, replace the default localhost in Host with the database service name.

TimescaleDB fields in Duaer

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

  • Host: Default: localhost.
  • Database: Default: postgres.
  • User: Default: postgres.
  • Password (secret)
  • Ignore SSL Issues (Insecure): Whether to connect even if SSL certificate validation is not possible. Default: off.
  • SSL: Default: Disable. Options: Allow, Disable, Require. Shown when Ignore SSL Issues (Insecure) is off.
  • Port: Default: 5432.

Duaer nodes that use it: TimescaleDB.

Save the connection in Duaer

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

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

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

In this section