Barbican is a ReST API designed for the secure storage, provisioning and management of secrets, including in OpenStack environments.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Douglas Mendizábal 3c2a99604a Update Back End Documentation 1 month ago
api-guide/source Add doc8 to pep8 check for project 10 months ago
barbican Imported Translations from Zanata 2 months ago
bin Update json module to jsonutils 3 months ago
devstack Update to opendev 2 months ago
doc Update Back End Documentation 1 month ago
etc Use default policy in code 1 year ago
functionaltests Update json module to jsonutils 3 months ago
playbooks/legacy OpenDev Migration Patch 2 months ago
releasenotes Merge "Update master for stable/stein" 1 month ago
.coveragerc Update .coveragerc after the removal of respective directory 2 years ago
.gitignore Switch to stestr 11 months ago
.gitreview OpenDev Migration Patch 2 months ago
.mailmap Add .mailmap file 5 years ago
.stestr.conf Switch to stestr 11 months ago
.zuul.yaml Gate jobs are voting 1 month ago
HACKING.rst Update json module to jsonutils 3 months ago
LICENSE Update LICENSE 6 years ago
README.md add release notes to README.rst 1 year ago
apiary.apib Correct a typo in apiary.apib 3 years ago
babel.cfg Merge of previous project work into this project 6 years ago
bindep.txt Fix pep8 gate failure because of missing dependency 2 years ago
lower-constraints.txt Add barbican-status upgrade check command framework 5 months ago
requirements.txt Block bandit 1.6.0 1 month ago
setup.cfg Dropping the py35 testing 2 months ago
setup.py Updated from global requirements 2 years ago
test-requirements.txt Block bandit 1.6.0 1 month ago
tox.ini Merge "Dropping the py35 testing" 1 month ago

README.md

Team and repository tags

Team and repository tags

Barbican

Barbican is a REST API designed for the secure storage, provisioning and management of secrets. It is aimed at being useful for all environments, including large ephemeral Clouds.

Barbican is an OpenStack project developed by the Barbican Project Team with support from Rackspace Hosting, EMC, Ericsson, Johns Hopkins University, HP, Red Hat, Cisco Systems, and many more.

The full documentation can be found on the Barbican Developer Documentation Site.

If you have a technical question, you can ask it at Ask OpenStack with the barbican tag, or you can send an email to the OpenStack General mailing list at openstack@lists.openstack.org with the prefix [barbican] in the subject.

To file a bug, use our bug tracker on OpenStack Storyboard.

Release notes for the project can be found at( https://docs.openstack.org/releasenotes/barbican).

For development questions or discussion, hop on the OpenStack-dev mailing list at openstack-dev@lists.openstack.org and let us know what you think, just add [barbican] to the subject. You can also join our IRC channel #openstack-barbican on Freenode.

Barbican began as part of a set of applications that make up the CloudKeep ecosystem. The other systems are:

  • Postern - Go based agent that provides access to secrets from the Barbican API.
  • Palisade - AngularJS based web ui for the Barbican API.
  • Python-barbicanclient - A convenient Python-based library to interact with the Barbican API.

Getting Started

Please visit our Users, Developers and Operators documentation for details.

Why Should You Use Barbican?

The current state of key management is atrocious. While Windows does have some decent options through the use of the Data Protection API (DPAPI) and Active Directory, Linux lacks a cohesive story around how to manage keys for application use.

Barbican was designed to solve this problem. The system was motivated by internal Rackspace needs, requirements from OpenStack and a realization that the current state of the art could use some help.

Barbican will handle many types of secrets, including:

  • Symmetric Keys - Used to perform reversible encryption of data at rest, typically using the AES algorithm set. This type of key is required to enable features like encrypted Swift containers and Cinder volumes, encrypted Cloud Backups, etc.
  • Asymmetric Keys - Asymmetric key pairs (sometimes referred to as public / private keys) are used in many scenarios where communication between untrusted parties is desired. The most common case is with SSL/TLS certificates, but also is used in solutions like SSH keys, S/MIME (mail) encryption and digital signatures.
  • Raw Secrets - Barbican stores secrets as a base64 encoded block of data (encrypted, naturally). Clients can use the API to store any secrets in any format they desire. The Postern agent is capable of presenting these secrets in various formats to ease integration.

For the symmetric and asymmetric key types, Barbican supports full life cycle management including provisioning, expiration, reporting, etc. A plugin system allows for multiple certificate authority support (including public and private CAs).

Design Goals

  1. Provide a central secret-store capable of distributing secret / keying material to all types of deployments including ephemeral Cloud instances.
  2. Support reasonable compliance regimes through reporting and auditability.
  3. Application adoption costs should be minimal or non-existent.
  4. Build a community and ecosystem by being open-source and extensible.
  5. Improve security through sane defaults and centralized management of policies for all secrets.
  6. Provide an out of band communication mechanism to notify and protect sensitive assets.