Skip to the content
Know your tech before you buy it. Makers: get listed from $49/mo

OpenStack Barbican

docs.openstack.org

  • Free plan
  • Linux
  • API
  • Self-hosted

What OpenStack Barbican is

OpenStack Barbican is a key manager service for storing, provisioning, and managing secrets such as encryption keys, certificates, passwords, and raw binary data. Its barbican-api component exposes an OpenStack-native REST API, while barbican-worker and barbican-keystone-listener are also part of the service. A plugin architecture lets operators connect software-based secret stores or hardware such as HSMs. Documented integrations include KMIP, Dogtag, Vault, and PKCS#11 crypto plugins; with PKCS#11, master encryption and HMAC keys can reside in an HSM. Operators can build custom plugins for secret storage, generation, and event handling, with support status varying between stable, experimental, or out-of-tree. The default Simple Crypto plugin stores its single encryption key in plaintext in barbican.conf, so service-node access needs careful restriction. Container ACL settings are not propagated to associated secrets, and ACL functionality applies only when Barbican is integrated with Keystone. Barbican is self-hosted, free, and provided under the Apache 2.0 license. Installation documentation assumes a working OpenStack deployment.

Who it suits

Barbican suits operators who need secret management within an OpenStack deployment and want to connect software stores or HSMs. It is also relevant to teams prepared to restrict access to service nodes and account for its ACL behavior.

Good to know, and what to watch

  • OpenStack-native REST API for managing secrets.
  • Plugin architecture supports software stores and HSMs.
  • PKCS#11 can keep master keys in an HSM.
  • Operators can develop custom storage and event plugins.
  • Free and provided under the Apache 2.0 license.
  • Installation documentation assumes a working OpenStack deployment.
  • Default encryption key is stored in plaintext in barbican.conf.
  • Container ACL settings do not propagate to associated secrets.
  • ACL functionality applies only with Keystone integration.

Open source Barbican

Free

Open source

Getting started

  1. Ensure a working OpenStack deployment is available
  2. Open the Barbican documentation website
  3. Deploy barbican-api, barbican-worker, and barbican-keystone-listener
  4. Choose a documented secret-store or cryptographic plugin
  5. Configure Keystone integration when ACL functionality is required
  6. Restrict access to service nodes when using the Simple Crypto plugin

The verdict

Barbican provides OpenStack secret management with plugin options for software stores and hardware security modules. Operators should review the default key storage and ACL limitations before deployment.

Questions people ask

What does OpenStack Barbican cost?

The Open source Barbican plan costs nothing and is free.

Which platforms does Barbican support?

It is available as a self-hosted Linux service with an API.

Which secret stores can it integrate with?

Documented plugins include KMIP, Dogtag, Vault, and PKCS#11 cryptographic plugins.

Can Barbican use hardware security modules?

Yes. The PKCS#11 plugin interfaces with an HSM and can keep master encryption and HMAC keys there.

Is Barbican open source?

Yes. The OpenStack project is provided under the Apache 2.0 license.

Does installation require OpenStack?

Yes. The installation documentation assumes a working OpenStack deployment.

What the maker publishes

ACL limitation
Container ACL settings are not propagated to associated secrets, and ACL functionality applies only when Barbican is integrated with Keystone. source
API
The barbican-api service provides an OpenStack-native REST API for provisioning and managing secrets. source
Components
The service includes barbican-api, barbican-worker, and barbican-keystone-listener components. source
Customization
Operators can develop custom plugins for secret storage, generation, and event handling; plugin support status can be stable, experimental, or out-of-tree. source
Deployment requirement
The installation documentation assumes a working OpenStack deployment. source
HSM support
The PKCS#11 crypto plugin interfaces with a Hardware Security Module, with master encryption and HMAC keys residing in the HSM. source
Integrations
Documented secret-store plugins include KMIP, Dogtag, and Vault, alongside PKCS#11 crypto plugins. source
Keystone
The Keystone listener manages Barbican database representations of Keystone projects when those projects are deleted. source
License
The OpenStack project is provided under the Apache 2.0 license. source
Purpose
Barbican is the OpenStack Key Manager service for secure storage, provisioning, and management of secrets such as keys, certificates, passwords, and raw binary data. source
Secret stores
A plugin architecture lets operators store secrets in software-based stores or hardware devices such as HSMs. source
Security tradeoff
The default Simple Crypto plugin stores its single encryption key in plaintext in barbican.conf, so access to service nodes must be restricted carefully. source

Checked against the maker's pages on 4 Oct 2026.