b06abac781
GET /cas/ would return all the CAs even if they're not in the project. This CR enables the behavior in which if project CAs are defined, then it will show them when running GET /cas/; If they're not, then it will show all CAs. On the other hand, this fixes an issue with remove-from-project. Where if you would remove the last CA from a project, it would still have a preferred one. So the behavior now is: If the user tries to delete the preferred CA; an error will be returned unless it is the last CA left for the project. Change-Id: I195ecc4ea6a8748e003fd17b219a727701e5e15d |
||
|---|---|---|
| barbican | ||
| bin | ||
| contrib/devstack | ||
| devstack | ||
| doc/source | ||
| etc | ||
| functionaltests | ||
| .coveragerc | ||
| .gitignore | ||
| .gitreview | ||
| .mailmap | ||
| .testr.conf | ||
| apiary.apib | ||
| babel.cfg | ||
| bandit.yaml | ||
| HACKING.rst | ||
| LICENSE | ||
| MANIFEST.in | ||
| openstack-common.conf | ||
| pylintrc | ||
| README.md | ||
| requirements.txt | ||
| setup.cfg | ||
| setup.py | ||
| test-requirements.txt | ||
| tox.ini | ||
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
- Provide a central secret-store capable of distributing secret / keying material to all types of deployments including ephemeral Cloud instances.
- Support reasonable compliance regimes through reporting and auditability.
- Application adoption costs should be minimal or non-existent.
- Build a community and ecosystem by being open-source and extensible.
- Improve security through sane defaults and centralized management of policies for all secrets.
- Out of band communication mechanism to notify and protect sensitive assets.