Duaer

Integrations

Set up Elasticsearch credentials in Duaer

Store Elasticsearch 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 Elasticsearch

The Duaer Elasticsearch API credential:

  • Base URL: on Elastic Cloud, copy the Elasticsearch endpoint from the deployment page, such as https://mydeployment.es.us-central1.gcp.cloud.es.io:9243. Self-hosted, use https://<host>:9200.
  • Username and Password: the built-in admin is elastic. Safer: create a user with rights on the relevant indices only, under Stack Management > Users in Kibana.
  • For a self-hosted cluster with a self-signed certificate, turn on Ignore SSL Issues (Insecure).

Elasticsearch API fields in Duaer

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

  • Username
  • Password (secret)
  • Base URL: Referred to as Elasticsearch 'endpoint' in the Elastic deployment dashboard.
  • Ignore SSL Issues (Insecure): Default: off.

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

Duaer nodes that use it: Elasticsearch.

Save the connection in Duaer

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

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

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

In this section