mirror of
https://github.com/hashicorp/vault.git
synced 2026-02-11 19:01:12 +01:00
a087f7b267
Add support for testing `+ent.hsm` and `+ent.hsm.fips1402` Vault editions with `pkcs11` seal types utilizing a shared `softhsm` token. Softhsm2 is a software HSM that will load seal keys from a local disk via pkcs11. The pkcs11 seal implementation is fairly complex as we have to create a one or more shared tokens with various keys and distribute them to all nodes in the cluster before starting Vault. We also have to ensure that each sets labels are unique. We also make a few quality of life updates by utilizing globals for variants that don't often change and update base versions for various scenarios. * Add `seal_pkcs11` module for creating a `pkcs11` seal key using `softhsm2` as our backing implementation. * Require the latest enos provider to gain access to the `enos_user` resource to ensure correct ownership and permissions of the `softhsm2` data directory and files. * Add `pkcs11` seal to all scenarios that support configuring a seal type. * Extract system package installation out of the `vault_cluster` module and into its own `install_package` module that we can reuse. * Fix a bug when using the local builder variant that mangled the path. This likely slipped in during the migration to auto-version bumping. * Fix an issue where restarting Vault nodes with a socket seal would fail because a seal socket sync wasn't available on all nodes. Now we start the socket listener on all nodes to ensure any node can become primary and "audit" to the socket listner. * Remove unused attributes from some verify modules. * Go back to using cheaper AWS regions. * Use globals for variants. * Update initial vault version for `upgrade` and `autopilot` scenarios. * Update the consul versions for all scenarios that support a consul storage backend. Signed-off-by: Ryan Cragun <me@ryan.ec>
32 lines
1.1 KiB
Bash
32 lines
1.1 KiB
Bash
#!/bin/bash
|
|
# Copyright (c) HashiCorp, Inc.
|
|
# SPDX-License-Identifier: BUSL-1.1
|
|
|
|
set -ex
|
|
|
|
fail() {
|
|
echo "$1" 1>&2
|
|
exit 1
|
|
}
|
|
|
|
# If we're not given keys we'll short circuit. This should only happen if we're skipping distribution
|
|
# because we haven't created a token or keys.
|
|
if [ -z "$TOKEN_BASE64" ]; then
|
|
echo "TOKEN_BASE64 environment variable was unset. Assuming we don't need to distribute our token" 1>&2
|
|
exit 0
|
|
fi
|
|
|
|
[[ -z "$SOFTHSM_GROUP" ]] && fail "SOFTHSM_GROUP env variable has not been set"
|
|
[[ -z "$TOKEN_DIR" ]] && fail "TOKEN_DIR env variable has not been set"
|
|
|
|
# Convert our base64 encoded gzipped tarball of the softhsm token back into a tarball.
|
|
base64 --decode - > token.tgz <<< "$TOKEN_BASE64"
|
|
|
|
# Expand it. We assume it was written with the correct directory metadata. Do this as a superuser
|
|
# because the token directory should be owned by root.
|
|
sudo tar -xvf token.tgz -C "$TOKEN_DIR"
|
|
|
|
# Make sure the vault user is in the softhsm group to get access to the tokens.
|
|
sudo usermod -aG "$SOFTHSM_GROUP" vault
|
|
sudo chown -R "vault:$SOFTHSM_GROUP" "$TOKEN_DIR"
|