🛡️ A private certificate authority (X.509 & SSH) & ACME server for secure automated certificate management, so you can use TLS everywhere & SSO for SSH.
I expected it to use my password file and automatically decrypt the key like it does when generating a new cert.
Actual Behavior
It doesn't appear to use my password file and automatically decrypt the key like it does when generating a new cert. This breaks my automation when using an existing cert because now it's looking for a user prompt.
Additional Context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).
Steps to Reproduce
Generate a root certificate
Now, move it somewhere else and try to generate a new one using that existing root
Your Environment
step-ca
Version - 0.26.1Expected Behavior
I expected it to use my password file and automatically decrypt the key like it does when generating a new cert.
Actual Behavior
It doesn't appear to use my password file and automatically decrypt the key like it does when generating a new cert. This breaks my automation when using an existing cert because now it's looking for a user prompt.
Additional Context
No response
Contributing
Vote on this issue by adding a 👍 reaction. To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).