Duaer

Integrations

Set up Microsoft Azure Cosmos DB credentials in Duaer

Store Microsoft Azure Cosmos DB 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 the Azure Cosmos DB account key

The Duaer Microsoft Azure Cosmos DB API credential:

  1. In the Azure portal, open the Keys page of the Cosmos DB account (NoSQL API) and copy PRIMARY KEY into Key. For read-only use, take a Read-only key.
  2. Account is the account name: the part in https://<account>.documents.azure.com. Database is the database name.

Microsoft Azure Cosmos DB API fields in Duaer

In Duaer, choose Microsoft Azure Cosmos DB API when you create a credential, then fill in these fields:

  • Account (required): Account name.
  • Key (required, secret): Account key.
  • Database (required): Database name.

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

Duaer nodes that use it: Azure Cosmos DB.

Save the connection in Duaer

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

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

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

In this section