Replies: 2 comments
-
Hey @merlinz01, yes, it looks like you're on the right track. I haven't tried your code yet, but it looks like it should work, or is at least close to working; does it work for you? In terms of documentation: yeah, we're aware the CA API isn't documented fully / neatly. The best way is to read the CLI for some reference code, which I believe you've already done. Depending on your requirements, and given that your HTTP server is able to reach the CA, maybe using the ACME provisioner is an alternative for you? But in that case you'll need the HTTP server and CA to be on the same network, or use a DNS challenge. The nice thing about it is that it's a standardized protocol that's well documented. |
Beta Was this translation helpful? Give feedback.
-
Yes, I am getting it to work. The ACME and DNS provisioners are not an option in this case which is why I am using the JWK provisioner. Now a question: will my code (or the step CLI) succeed in renewing a certificate that has expired? Will I have to manually update the certificate if it expires while this server is down? |
Beta Was this translation helpful? Give feedback.
-
I am trying to integrate step PKI into my web servers via the Go API, but I am having trouble figuring out the right way to do it.
What I need to do is this:
I should only need to send the provisioner password to the server once when initializing it; I don't want to send the provisioner password to all my servers every time they restart. The rest of the time it should simply renew the certificate.
Here's what I have so far:
The question
Am I on the right track, or am I reinventing the wheel or doing something stupid?
I would really appreciate better documentation of the API.
Beta Was this translation helpful? Give feedback.
All reactions