> For the complete documentation index, see [llms.txt](https://doc.duaer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.duaer.com/integrations/builtin/credentials/kibana.md).

# Set up Kibana credentials in Duaer

Store Kibana 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 Kibana <a href="#connect-to-kibana" id="connect-to-kibana"></a>

The Duaer Kibana API credential:

- URL is the Kibana address, such as http://localhost:5601; on Elastic Cloud, use the Kibana endpoint from the deployment page.
- Username and Password are a user with the Kibana privileges you need, ideally not the elastic superuser.

Duaer has no dedicated node for this service. In the HTTP Request node, set Authentication to Predefined Credential Type and pick the Kibana API credential. Refer to [custom operations](/integrations/custom-operations.md).

## Kibana API fields in Duaer <a href="#kibana-api" id="kibana-api"></a>

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

- URL (required)
- Username (required)
- Password (required, secret)

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

## Save the connection in Duaer

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

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

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