Hello,
Great work, and very helpful to the community.
I create my certificates using a certificate authority without a challenge (that’s not the problem, but there is no doc about it). Then I want to export them to my servers that need them. Using a Docker container on my servers is out of the question (load, security, etc.).
I have two options left:
- Either use bulk export using the certificate’s API keys
(I have a working prototype with a script that reads a
config file containing all the references to my certificates; the format is:
server.mydomain.com|certAPI123xxxx|keyAPIabc1111|root@sever.mydomain.com|sudo systemctl reload nginx)
It works, but I end up with practically a copy of the CertWarden database in text format—which is totally stupid and insecure.
-Or use the per-certificate export with post-processing.
Problem: You have to define all the necessary variables, which means a lot of clicking: (Is this a Microsoft Windows product? :-})
I tried defining everything on a single line, but it doesn’t work (which just goes to show how secure CertWarden is) (e.g., CW_CERT_NAME={{CERTIFICATE_NAME}} CW_CERT_PEM={{CERTIFICATE_PEM}} CW_KEY_PEM={{PRIVATE_KEY_PEM}} in the input)
There should be a “Export All Vars” checkbox. To clarify my point, let’s consider the opposite scenario—a script that doesn’t use any variables from CertWarden: what would be the point of it?
Thank you for your insightful responses
