Step CA Pro offers a “linked” deployment type and can operate as a standalone or clustered CA.
Linking Step CA Pro
with Smallstep and Smallstep RunAnywhere
Step CA Pro offers a “linked” deployment type in addition to its ability to operate as a standalone or clustered CA. When running in linked mode, Step CAPro will work in conjunction with the Smallstep platform to propagate provisioner configuration, admins, certificates, and revocations from the Step CA Pro instance.
Existing Step CA Pro instances can be linked to Smallstep or Smallstep RunAnywhere, but any existing artifacts from CA operations (for example, certificates) will not be propagated. Artifacts from operations after the linking is performed will be propagated as normal.
Step CA Pro performs propagation of changes in a resilient manner that can recover from common operational impairments that would make Smallstep or Smallstep RunAnywhere unavailable to the Step CA Pro instance.
Step-by-step Guide
- Prepare your PKI
- For a new authority, run
step ca init --name "my-authority" --deployment-type linked
, follow the prompts, and save the private key passphrase somewhere safe. Ensureca.json
has the correct configuration for any optional customization, such as HSM support with PKCS#11 URIs for key management.
- For existing authorities, ensure you have your
ca.json
file, your root and any intermediates, and the private key passphrase prepared
- For a new authority, run
- Create a linked authority in Smallstep or Smallstep RunAnywhere
- Under
Certificate Manager
, clickAuthorities
- Click
Add Authority
- Click
Link a step-ca instance
- Choose
Pro
from the “step-ca Edition” dropdown, and clickNext
- Copy the token from the
step-ca
command shown
- Under
- Initialize Step CA Pro
- Ensure your database is set up and ready for Step CA Pro, consult the Step CA Pro documentation for details
- Ensure you have the token from step #2
step-ca-pro init --name "my-authority" --driver ... --database ... --token ...
- Save the generated admin provisioner passphrase somewhere safe
- Edit the
ca.json
and add the generated authority ID:{
"...": "...",
"authority": {
"authorityId": "<authority-id>"
}
}
- Start Step CA Pro
step-ca-pro start --password-file <path-to-private-key-passphrase> --token ... <path-to-ca-json>
- Use
step
to interact with your Step CA Pro instance- eg:
step ca certificate ...
- eg: