This patch changes the slot selection logic to look for more than one token label in the list of slots, using the first token that is found. This change is required to enable load balancing with devices that use separate tokens for this feature. This patch adds a new option in the [p11_crypto_plugin] section "token_labels", and deprecates the "token_label" option. For backwards compatibility, the "token_label" option will still be used if present. Change-Id: Ic2b85246c37e856c38cb47613313b19e653118de
|1 week ago|
|api-guide/source||4 months ago|
|barbican||3 days ago|
|bin||2 years ago|
|devstack||6 months ago|
|doc||1 month ago|
|etc||10 months ago|
|functionaltests||4 months ago|
|playbooks/legacy||6 months ago|
|releasenotes||3 days ago|
|.coveragerc||4 years ago|
|.gitignore||2 years ago|
|.gitreview||1 year ago|
|.mailmap||7 years ago|
|.stestr.conf||2 years ago|
|.zuul.yaml||5 months ago|
|HACKING.rst||2 years ago|
|LICENSE||8 years ago|
|README.rst||5 months ago|
|apiary.apib||1 year ago|
|bindep.txt||6 months ago|
|requirements.txt||1 month ago|
|setup.cfg||1 month ago|
|setup.py||10 months ago|
|test-requirements.txt||1 month ago|
|tox.ini||4 months ago|
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 <http://www.rackspace.com/>_, 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.
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.
Future design work is tracked at https://specs.openstack.org/openstack/barbican-specs.
For development questions or discussion, use the OpenStack-discuss mailing list at email@example.com and let us know what you think, just add [barbican] to the subject. You can also join our IRC channel #openstack-barbican on Freenode.
Please visit our Users, Developers and Operators documentation for details.
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:
For the symmetric and asymmetric key types, Barbican supports full life cycle management including provisioning, expiration, reporting, etc.