# Secrets

## Overview

OpenStack Cloud uses the component Barbican for secret storage. We introduced the Barbican secret storage to provide a safe way to store SSL certificates and private keys for [Octavia Load balancer as a Service](<https://documentation.syseleven.de/en/prior-docs/openstack-cloud/reference/network/lbaas/index.md>) The barbican secret storage is part of our global region. This means, similar to [Keystone (Identity and Access)](<https://documentation.syseleven.de/en/prior-docs/openstack-cloud/reference/identity-and-access/index.md>) there is one API for all regions.

| Barbican feature | Supported |
| --- | --- |
| Secret storage and metadata | Yes |
| Containers | Yes |
| Access control lists | Yes |
| Certificate orders | No |

## Secret Storage and Metadata

All secrets are transferred and stored fully encrypted. Metadata may not be stored fully encrypted.

## Containers

Containers represent a set of secrets, for a certain purpose.

Containers can be of type `generic`, `RSA`, or `Certificate`.

| Type | Accompanied secret names |
| --- | --- |
| Generic | No restrictions |
| RSA | `public_key`, `private_key`, and `private_key_passphrase` |
| Certificate | `certificate` and optionally `private_key`, `private_key_passphrase`, and `intermediates` |

## Access Control Lists

By default, secrets and containers are accessible for all users of a project (See the [identity and access reference guide](<https://documentation.syseleven.de/en/prior-docs/openstack-cloud/reference/identity-and-access/index.md>) for more information about users, groups and projects). Using access control lists, you can reduce access to certain users or groups.

> [!NOTE]
>
> **Info**
>
> Currently the access control list (ACL) settings defined for a container are not propagated down to associated secrets.

## Known Issues

- Currently it is not possible to create containers of type certificate with Terraform. See [the Terraform issue tracker](<https://github.com/terraform-provider-openstack/terraform-provider-openstack/issues>) and the [OpenStack issue tracker](<https://storyboard.openstack.org/#!/story/2007629>).
