Duaer

Integrations

Set up Cortex credentials in Duaer

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

Get a Cortex API key

The Duaer Cortex API credential:

  1. On the Cortex Organization page, click Create API Key for a user with the analyze role and copy it.
  2. Put it in API Key. Put the instance address, such as https://cortex.example.com:9001, in Cortex Instance.

Cortex API fields in Duaer

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

  • API Key (secret)
  • Cortex Instance: The URL of the Cortex instance.

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

Duaer nodes that use it: Cortex.

Save the connection in Duaer

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

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

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

In this section