step-ca package, and the step-kms-plugin. Then pull the container image that serves the CA.
The
step-ca package you install here provides the host toolchain. It cannot serve the CA in this integration because official builds are compiled without PKCS #11 support. The smallstep/step-ca:hsm image at the end of this page is what runs the CA.Install the step CLI and step-ca
1
Download the current Debian packages:
Shell
These URLs fetch the current releases rather than a pinned version. The validated versions for this guide are in the table on Before you start.
2
Install both packages:
Shell
3
Verify the installation:
Shell
Each command prints its version and platform. The validated run reported the following:
Shell
Install the step-kms-plugin
The step-kms-plugin adds thestep kms subcommand, which the step CLI uses to address keys held in an external key management system, including PKCS #11 tokens.
1
Download and install the plugin package:
Shell
This command pins step-kms-plugin
0.15.1, the validated version. If you install a later release, adjust both the URL and the file name to match the release you downloaded.2
Verify the plugin registered with the step CLI:
Shell
The step CLI prints the
step kms usage text with its subcommands, including create, key, and sign. If the CLI reports an unknown command, the plugin did not install.Pull the PKCS #11-capable container image
1
Pull the
:hsm image:Shell
:hsm is a moving tag. Pulling it again later can retrieve a newer step-ca build. The validated run used step-ca 0.30.2 from this image.2
Verify the image runs and reports a version:
Shell
The container prints the step-ca version from the image, for example
Smallstep CA/0.30.2 (linux/amd64).The
--entrypoint step-ca flag is required every time you run a step-ca command in this image. The image’s default entrypoint is a startup script that expects a full CA bootstrap environment, so it does not pass your arguments through to the step-ca binary. The same flag appears in the run command on Start step-ca.
