Supported hardware
- CryptoHub,
7.0.3.xor later.
Supported operating systems
- Linux
This guide is Linux only. The
smallstep/step-ca:hsm image is a Linux container and cannot load the Windows FXPKCS11 library, so no Windows path is documented for the long-running CA.Required access
- An account on the CryptoHub with administrator permissions to deploy new services.
- Local administrator/root access on the computer where step-ca runs.
Network and firewall
- Allow outbound TCP port 2001 (default Host API port) from the computer running step-ca to the CryptoHub, specified by FQDN (for example,
cryptohub.example.com) or CIDR (for example,10.0.0.0/24). - Allow inbound HTTPS on TCP port 9000 from the clients that request certificates to the step-ca host.
- Ensure DNS resolution is available for the CryptoHub address and for the DNS names you configure on the CA.
Required software
- Docker, to run the
smallstep/step-ca:hsmimage. - The step CLI (
step). - The step-kms-plugin (
step kms). - The
step-capackage, for the host toolchain. - The Futurex PKCS #11 (FXPKCS11) module, delivered in the CryptoHub endpoint ZIP.
- OpenSSL, for independent signature and certificate chain verification.
pkcs11-tool, available in theopenscpackage.
Validated toolchain
The following versions were validated end to end for this guide. Later releases in the same series are expected to work, but these are the versions the documented commands and output were confirmed against.The download commands in Install step-ca and the step CLI fetch the current Smallstep releases, and
smallstep/step-ca:hsm is a moving tag rather than a pinned version. Expect versions later than the table above. If a command in this guide behaves differently, compare your installed versions against this table first.
