openstack/barbican
Code Issues Proposed changes
Barbican is a ReST API designed for the secure storage, provisioning and management of secrets, including in OpenStack environments.
3,005 Commits 12 Branches 62 Tags 39 MiB
Python 98.1%
Shell 1.8%
aafeb7aa91
Go to file
Juan Antonio Osorio Robles aafeb7aa91 Enforce usage of oslo.context's project_id 
Instead of using "project" which came from our legacy custom context
class, we enforce the usage of oslo.context's project_id. Thus cleaning
up that class a little bit.

Change-Id: Ic030f426de744c585ca6b4a02f0a9e6b6df15cc5
2018-04-23 17:37:52 +03:00
api-guide/source Merge "Update the documentation link for doc migration" 2017-11-14 07:51:12 +00:00
api-ref/source Use openstackdocstheme 1.11 everywhere 2017-06-30 20:12:52 +02:00
barbican Enforce usage of oslo.context's project_id 2018-04-23 17:37:52 +03:00
bin Merge "Debug with barbican-api" 2017-04-05 15:12:18 +00:00
devstack Merge "Set debug mode according to ENABLE_DEBUG_LOG_LEVEL" 2018-04-16 20:06:03 +00:00
doc/source Merge "Update the link in database_migrations.rst" 2018-04-16 20:24:26 +00:00
etc Use default policy in code 2018-02-09 08:16:43 +00:00
functionaltests Updating time for functional tests 2018-03-08 13:38:23 +07:00
playbooks/legacy Migrate to Zuul v3 2017-10-30 05:37:24 +00:00
releasenotes Imported Translations from Zanata 2018-04-19 06:45:07 +00:00
.coveragerc Update .coveragerc after the removal of respective directory 2016-10-17 17:37:58 +05:30
.gitignore Add sample config and policy to documentation 2018-02-09 08:16:03 +00:00
.gitreview Update .gitreview file for new repo name 2014-05-23 18:14:46 -04:00
.mailmap Add .mailmap file 2013-12-02 11:23:23 -05:00
.testr.conf Adds true functional tests for db_manage script 2016-08-05 16:28:52 -05:00
.zuul.yaml Merge "Update to fedora-27 for testing" 2018-03-23 19:07:41 +00:00
apiary.apib Correct a typo in apiary.apib 2016-06-10 14:56:19 +00:00
babel.cfg Merge of previous project work into this project 2013-04-01 18:26:03 -05:00
bindep.txt Fix pep8 gate failure because of missing dependency 2017-06-08 11:37:24 +07:00
HACKING.rst Update the documentation link for doc migration 2017-10-11 18:11:17 +08:00
LICENSE Merge of previous project work into this project 2013-04-01 18:26:03 -05:00
lower-constraints.txt Add os-testr as test dependency 2018-04-11 18:29:56 +08:00
README.md Update the documentation link for doc migration 2017-10-11 18:11:17 +08:00
requirements.txt Add os-testr as test dependency 2018-04-11 18:29:56 +08:00
setup.cfg Do not copy policy.json when installing barbican 2018-03-23 17:28:51 +08:00
setup.py Updated from global requirements 2017-03-06 01:07:50 +00:00
test-requirements.txt Add os-testr as test dependency 2018-04-11 18:29:56 +08:00
tox.ini Apply pep8 check to app.wsgi 2018-04-11 14:38:06 +07:00

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 Launchpad.

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.