Duaer

Integrations

Set up TheHive credentials in Duaer

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

Choose a TheHive credential type

Duaer uses two credentials, depending on the TheHive version. Both need an API key and the instance address:

  • The Hive 5 API: for the TheHive node on TheHive 5. Open a user on the organization Users page and click Create to generate an API key.
  • The Hive API: for the older node on TheHive 3 and 4; set API Version to match. Generate the key under the user’s API Key.

URL is the instance root, such as https://thehive.example.com:9000. Turn on Ignore SSL Issues (Insecure) for a self-signed certificate.

The key carries all of its creator’s permissions. For a workflow, generate it from a dedicated account with the fewest rights needed.

The Hive 5 API

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

  • API Key (secret)
  • URL: The URL of TheHive instance.
  • Ignore SSL Issues (Insecure): Whether to connect even if SSL certificate validation is not possible. Default: off.

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

The Hive API

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

  • API Key (secret)
  • URL: The URL of TheHive instance.
  • API Version: The version of api to be used. Options: TheHive 4+ (api v1), TheHive 3 (api v0).
  • Ignore SSL Issues (Insecure): Whether to connect even if SSL certificate validation is not possible. Default: off.

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

Duaer nodes that use it: TheHive.

Save the connection in Duaer

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

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

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

In this section