Duaer

Integrations

Set up Venafi TLS Protect Cloud credentials in Duaer

Store Venafi TLS Protect Cloud 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 Venafi TLS Protect Cloud API key

The Duaer Venafi TLS Protect Cloud credential:

  1. In TLS Protect Cloud, open your avatar at the top right, go to Preferences > API Keys, copy the key, and put it in API Key.
  2. Set Region to where the account lives, US or EU.

Venafi TLS Protect Cloud Trigger registers a webhook with the service, so Duaer must be reachable from the internet.

Venafi TLS Protect Cloud fields in Duaer

In Duaer, choose Venafi TLS Protect Cloud when you create a credential, then fill in these fields:

  • Region: Default: US. Options: US, EU.
  • API Key (secret)

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

Duaer nodes that use it: Venafi TLS Protect Cloud, Venafi TLS Protect Cloud Trigger.

Save the connection in Duaer

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

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

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

In this section