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.
2,441 Commits 12 Branches 62 Tags 39 MiB
Python 98.1%
Shell 1.8%
b05c4b6f86
Go to file
Arun Kant b05c4b6f86 Central logic to sync secret store data with conf data (Part 3) 
Modified logic to retrieve applicable plugins when preferred project
is set.

This is part 2 of central logic changes needed for multiple backend
support work.

Change-Id: I15eb7ca88611a12677227647e3026822e67413b0
Partially-Implements: blueprint multiple-secret-backend
2016-09-14 06:49:53 -07:00
api-guide/source Fix the typo 2016-08-01 16:28:27 +08:00
barbican Central logic to sync secret store data with conf data (Part 3) 2016-09-14 06:49:53 -07:00
bin User with creator role can delete his/her own secret and container 2016-07-25 13:42:01 -07:00
devstack Remove "KEYSTONE_" URI settings for devsatck 2016-08-07 20:04:29 -05:00
doc/source Adding API docs for multiple backend support changes. 2016-09-07 11:24:08 -07:00
etc Changes for multiple backend conf and friendly plugin names (Part 2) 2016-09-14 06:49:29 -07:00
functionaltests Merge "Remove consumer check for project_id to match containers" 2016-09-13 17:52:42 +00:00
install-guide/source Add Barbican Verification to Install Guide 2016-08-28 06:23:30 +00:00
releasenotes standardize release note page ordering 2016-09-08 14:51:06 -04:00
.coveragerc Add I18n-related unit tests (Part 3) 2015-01-05 16:41:08 -06:00
.gitignore Update .gitignore for pyenv 2016-02-09 10:35:47 -06: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 Use testr for running functional tests and documentation 2015-09-14 11:56:48 -05: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
HACKING.rst Deduplicate HACKING.rst with docs.openstack.org/developer/hacking/ 2014-09-24 14:35:44 -07:00
LICENSE Merge of previous project work into this project 2013-04-01 18:26:03 -05:00
pylintrc Merge of previous project work into this project 2013-04-01 18:26:03 -05:00
README.md Reworded sentence fragment in the README 2016-01-18 15:15:14 -06:00
requirements.txt Updated from global requirements 2016-08-26 05:06:34 +00:00
setup.cfg Merge "modify the home-page info with the developer documentation" 2016-08-16 21:46:57 +00:00
setup.py Updated from global requirements 2015-09-18 20:41:35 +00:00
test-requirements.txt Updated from global requirements 2016-08-26 05:06:34 +00:00
tox.ini Support upper-constratints.txt in tox environments 2016-08-22 15:33:49 +10:00

README.md

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 Getting Started wiki page 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.