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]: unable to initialize #1642

Open
ctron opened this issue Dec 11, 2023 · 4 comments
Open

[Bug]: unable to initialize #1642

ctron opened this issue Dec 11, 2023 · 4 comments
Assignees
Labels
bug needs triage Waiting for discussion / prioritization by team

Comments

@ctron
Copy link

ctron commented Dec 11, 2023

Steps to Reproduce

Run any step-ca command.

Your Environment

  • OS - Fedora 39
  • step-ca Version - CA/0.25.2

Expected Behavior

It gives instruction that work.

Actual Behavior

I get:

step-ca can't find or open the configuration file for your CA.
You may need to create a CA first by running `step ca init`.
Documentation: https://u.step.sm/docs/ca

Running step-ca init brings the same message.

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

@ctron ctron added bug needs triage Waiting for discussion / prioritization by team labels Dec 11, 2023
@hslatman
Copy link
Member

hslatman commented Dec 11, 2023

Hi @ctron,

To create a configuration for the CA, you'll need to install the step CLI and use that as step ca init. This will create a CA configuration file, which can then be used to run step-ca.

@ctron
Copy link
Author

ctron commented Dec 11, 2023

That feels a bit weird.

@hslatman
Copy link
Member

hslatman commented Dec 11, 2023

I agree it can be a bit surprising and that it adds a bit more friction to getting started to using the CA, especially if you're using the CA for the first time, but step and step-ca are different components with different responsibilities. I would say they're somewhat similar in nature as systemctl and systemd.

An improvement I can imagine we could add is to look for step in the path when this message is returned to the user. If it's not found, we could suggest the user to install it. But note that the message already says step ca init; not step-ca init.

@ctron
Copy link
Author

ctron commented Dec 11, 2023

An improvement I can imagine we could add is to look for step in the path when this message is returned to the user. If it's not found, we could suggest the user to install it. But note that the message already says step ca init; not step-ca init.

Yes, that would definitely help.

@hslatman hslatman self-assigned this Dec 12, 2023
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