Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: step ca init ignores --password-file when using an existing root cert #1888

Open
stew3254 opened this issue Jun 15, 2024 · 0 comments
Assignees
Labels
bug needs triage Waiting for discussion / prioritization by team

Comments

@stew3254
Copy link

Steps to Reproduce

Generate a root certificate

cd ~
echo "test" > passwd
step ca init --deployment-type standalone --password-file passwd --dns ca.home --name Homelab --address :443 --provisioner JWK

Now, move it somewhere else and try to generate a new one using that existing root

cd ~
mv .step step
step ca init --deployment-type standalone --password-file passwd --dns ca.home --name Homelab --address :443 --provisioner JWK --root step/certs/root_ca.crt --key step/secrets/root_ca_key

Your Environment

  • OS - Ubuntu 22.04.4
  • step-ca Version - 0.26.1

Expected 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).

@stew3254 stew3254 added bug needs triage Waiting for discussion / prioritization by team labels Jun 15, 2024
@hslatman hslatman self-assigned this Jun 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug needs triage Waiting for discussion / prioritization by team
Projects
None yet
Development

No branches or pull requests

2 participants