Integrations
Set up Elastic Security credentials in Duaer
Store Elastic Security 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.
Connect to Elastic Security
The Duaer Elastic Security API credential connects to Kibana, not Elasticsearch:
- Base URL: copy the Kibana endpoint from the Elastic Cloud deployment page, such as https://mydeployment.kb.us-central1.gcp.cloud.es.io:9243.
- With Type set to API Key, create a key under Stack Management > API keys in Kibana and put it in API Key. With Basic Auth, use a user name and password that have Security privileges.
Elastic Security API fields in Duaer
In Duaer, choose Elastic Security API when you create a credential, then fill in these fields:
- Base URL (required): Referred to as Kibana 'endpoint' in the Elastic deployment dashboard.
- Type: Default: Basic Auth. Options: API Key, Basic Auth.
- Username (required): Shown when Type is Basic Auth.
- Password (required, secret): Shown when Type is Basic Auth.
- API Key (required, secret): Shown when Type is API Key.
When you save, Duaer tests the connection with these values.
Duaer nodes that use it: Elastic Security.
Save the connection in Duaer
Open Credentials and create Elastic Security. 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 Elastic Security secret values appear in Duaer node parameters?
No. In Duaer, Elastic Security secrets stay in the credential. Nodes only reference the credential. Execution records should not show the plaintext secret either.
What usually stops a Elastic Security 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 Elastic Security expects, then confirm you can create credentials in that project.
In this section
Built-in integrations in Duaer
Built-in triggers, actions, and credentials in Duaer. Triggers start a workflow. Actions run a step after it has started.
IntegrationsRisks of community nodes in Duaer
Before you install a community node in Duaer, know the code comes from a source the instance admin trusts, and know what permissions it gets.
IntegrationsTroubleshoot community nodes in Duaer
When a Duaer community node will not install or run, check the version, permissions, and node docs, then the instance logs.
IntegrationsMake custom API calls for an app in Duaer
When a Duaer app node does not expose the API you need, use HTTP Request and reuse that app’s saved authentication.
IntegrationsIntegrations in Duaer
Built-in triggers, actions, and credentials in Duaer. Community nodes are extra packages. Custom operations reuse saved authentication with HTTP Request.
CredentialsBuilt-in credentials in Duaer
Per-service credential notes for Duaer built-ins. The create flow is in the credentials overview; node docs link to the matching service page.
Create nodesCreate a custom node for Duaer
Write a node package for Duaer when built-in nodes and custom operations are not enough and you will reuse the step.