Skip to main content

​
Connecting HashiCorp Vault to Prizm

Before starting, complete the Vault prerequisites to enable App Role authentication and generate a Role ID and Secret ID in your Vault instance.
1

Open Integration settings

Navigate to Organization → Integration and click the + icon to open the Channels catalog. Click the Vault filter tab, then click the HashiCorp tile to open the configuration form.
Channels page listing the available integrations with All, Notification, Catalog, Collaboration and Vault filters

Organization → Integration → + opens the Channels catalog

2

Enter a name and optional description

Enter a display Name for this vault connection (e.g., Production Vault). Optionally add a Description to distinguish it from other vault integrations.
3

Enter the Vault address

Enter the full URL of your Vault instance in Vault Address, including the port if non-standard:
  • HCP Vault: Your HCP Vault public cluster address (e.g., https://vault-cluster.vault.hashicorp.cloud:8200)
  • Self-hosted: https://vault.yourcompany.com:8200
4

Select authentication type and namespace

Authentication Type is pre-set to App Role. Enter your Vault namespace in Namespace (e.g., admin for HCP Vault or a Vault Enterprise namespace). The form marks this field as required.
5

Enter Role ID and Secret ID

Paste the Role ID and Secret ID from the prerequisites step.
6

Enter the secret engine (optional)

If your secrets are stored under a non-default KV mount point (e.g., kv instead of secret), enter it in Secret Engine. Leave blank to use the default path.
7

Save the configuration

Click Create Integration. The button stays disabled until every required field is filled. When you reopen an existing integration to edit it, the same button reads Update Integration. Prizm authenticates with Vault and confirms it can reach the configured paths.
HashiCorp Vault Integration form with Name, Description, Vault Address, Authentication Type and Namespace fields

Add Integration form for HashiCorp Vault (top of the form)

HashiCorp Vault Integration form showing Role ID, Secret ID and Secret Engine fields

Role ID, Secret ID and Secret Engine fields

​
Configuration reference

When you rotate the Secret ID in Vault, update it in Prizm before invalidating the old one to avoid connector authentication failures.