Replies: 2 comments 2 replies
-
As an alternative, one thing you could try is a more extended form of
I think this form of the command doesn't depend on Another option would be to look at smallstep/clients as a reference point for generating your own tokens programmatically. By the way, in step 2 you are connecting to the CA insecurely for the sign operation. I'd strongly recommend passing a |
Beta Was this translation helpful? Give feedback.
-
@tashian thanks! but unfortunatelly, your suggestion does not work. still returns without the import, I opened pull request for this. smallstep/cli#828 this version of step cli can generate ott for hsm-enabled step-ca instance. (you need to build step cli with CGO, like hope it helps |
Beta Was this translation helpful? Give feedback.
-
hi, I've setup step-ca along with hsm by following instruction of https://smallstep.com/docs/step-ca/configuration#pkcs-11
and all setup seems to finish. then we want to generate our certficate via Web API, not from CLI.
without hsm, our steps to generate certificate via API is like following and it works fine.
step ca token --offline
CLI (it will be replaced with our program later stage of development)curl -k https://our_step_ca_host/sign -d '{"csr":$csr,"ott":$ott}'
but after step-ca setup along with hsm, step 1 is failed with
unsupported kms type ‘pkcs11'
with hsm, how can I generate cert via Web API? is it step-ca's limitation or am I missing some important settings?
regards,
Beta Was this translation helpful? Give feedback.
All reactions