3dd00efb87
This patch adds a new parameter for deploying Barbican with
a Thales Luna Network HSM (LunasaClientIPNetwork).
LunasaClientIPNetwork can be used to register controller nodes
with the HSM using the controller's IP address on the given
network instead of its fqdn.
Co-Authored-By: Ade Lee <alee@redhat.com>
Depends-On: If0eb393ca970206cc95c7453641f33781eb698b2
Change-Id: I02d577939b0002b0e605ac0cbbda54e05e0b206f
(cherry picked from commit ead85251e9)
49 lines
2.6 KiB
YAML
49 lines
2.6 KiB
YAML
# A Heat environment file to enable the barbican PKCS11 crypto backend with
|
|
# a Lunasa HSM.
|
|
# Note that barbican needs to be enabled in order to use this.
|
|
parameter_defaults:
|
|
# In order to use this backend, you need to uncomment these values and
|
|
# provide the appropriate values.
|
|
#
|
|
# BarbicanPkcs11CryptoLogin: Password (PIN) to login to PKCS11 session
|
|
# BarbicanPkcs11CryptoSlotId: Slot Id for the HSM. Note that this parameter is only
|
|
# strictly required when setting up the Lunasa client in non-HA mode. In HA
|
|
# mode, whatever value is placed here will be overridden by the dynamically generated
|
|
# slot for the HA group created on the client.
|
|
# BarbicanPkcs11CryptoGlobalDefault: Whether this plugin is the global default plugin
|
|
#
|
|
# LunasaClientIPNetwork: (Optional) Network to be used by the controllers
|
|
# to connect to the HSM. By default this option is empty ('') and the
|
|
# controllers are registered on the HSM using the controller's FQDN.
|
|
# When this option is set, the controllers will be registered using the
|
|
# controller's IP on this network instead.
|
|
|
|
BarbicanPkcs11CryptoLibraryPath: '/usr/lib/libCryptoki2_64.so'
|
|
BarbicanPkcs11CryptoEncryptionMechanism: 'CKM_AES_CBC'
|
|
BarbicanPkcs11CryptoHMACKeyType: 'CKK_AES'
|
|
BarbicanPkcs11CryptoHMACKeygenMechanism: 'CKM_AES_KEY_GEN'
|
|
BarbicanPkcs11CryptoMKEKLabel: 'barbican_mkek_0'
|
|
BarbicanPkcs11CryptoMKEKLength: '32'
|
|
BarbicanPkcs11CryptoHMACLabel: 'barbican_hmac_0'
|
|
BarbicanPkcs11CryptoLunasaEnabled: true
|
|
BarbicanPkcs11CryptoEnabled: true
|
|
BarbicanPkcs11AlwaysSetCkaSensitive: true
|
|
|
|
LunasaVars:
|
|
# lunasa_client_tarball_location: URI where the CipherTools tarball can be downloaded.
|
|
# lunasa_client_tarball_name: Filename for the CipherTools tarball.
|
|
# lunasa_client_installer_path: path to install.sh in the tarball.
|
|
# lunasa_client_rotate_cert: (Optional) Set to true to generate a new
|
|
# client certificate and re-register clients during deployment.
|
|
# lunasa_hsms: A list of HSMs. When more than one HSM is specified, they
|
|
# will be configured as an HA pool. Each entry should specify the
|
|
# following:
|
|
# - hostname: Hostname for the HSM
|
|
# admin_password: admin password for the HSM, used to add a new client.
|
|
# partition: HSM partition to be assigned to the clients.
|
|
# partition_serial: serial number for the partition.
|
|
# lunasa_ha_label: HA group label Required only for HA mode.
|
|
|
|
resource_registry:
|
|
OS::TripleO::Services::BarbicanBackendPkcs11Crypto: ../deployment/barbican/barbican-backend-pkcs11-crypto-puppet.yaml
|