Duaer

Integrations

Set up CrowdStrike credentials in Duaer

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

Create a CrowdStrike API client

The Duaer CrowdStrike OAuth2 API credential exchanges client credentials for a token:

  1. In the Falcon console, open Support and resources > API clients and keys, click Create API client, and tick only the API scopes you call.
  2. Put Client ID and Secret in the credential. The secret is shown once.
  3. Put your cloud region’s API address in URL, such as https://api.crowdstrike.com, https://api.us-2.crowdstrike.com, or https://api.eu-1.crowdstrike.com.

Duaer has no dedicated node for this service. In the HTTP Request node, set Authentication to Predefined Credential Type and pick the CrowdStrike OAuth2 API credential. Refer to custom operations.

CrowdStrike OAuth2 API fields in Duaer

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

  • URL (required)
  • Client ID (required)
  • Client Secret (required, secret)

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

Save the connection in Duaer

Open Credentials and create CrowdStrike. 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.

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 CrowdStrike secret values appear in Duaer node parameters?

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

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

In this section