> 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/vertica.md).

# Set up Vertica credentials in Duaer

Store Vertica 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.
## Fill in the Vertica credential <a href="#get-your-credentials" id="get-your-credentials"></a>

The Duaer Vertica API credential connects to the Vertica HTTPS service, port 8443 by default:

1. Put https://<host>:8443 in URL.
2. Put a database account with the needed rights in Username and Password.

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

When Duaer runs in Docker, do not use localhost for the host; use the service name or the host address.

## Vertica API fields in Duaer <a href="#vertica-api" id="vertica-api"></a>

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

- URL (required): Default: https://localhost:8443.
- Username: The username for accessing the Vertica database.
- Password (secret): The password for accessing the Vertica database.

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

## Save the connection in Duaer

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

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

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

