It's a bunch of command line scripts because if you are using it any different way you are probably doing it wrong.
It's a bunch of command line scripts because if you are using it any different way you are probably doing it wrong.
An API is required for you to have proper infrastructure as code and leaving any bit to human input other than another validation step in the automated process is waiting for errors to happen (invalid or incorrectly spelled cert info, missing cert chains, wrong cert chains, etc.).
Symantec even calls out how much work these companies will have to do because so few of them have a proper certificate management system in place that's come back to bite them.
This is the exact issue with the public CA system, their automated processes have been found lacking and now what they certify can not be trusted.
And you're missing the point I raised as well - if you have hosts coming up automatically, you either need automatic certificates, or shared keys. As long as you rely on SSL, there's no other way to go.
(For example of authentication: public CA verifies your domain, internal CA can ask the hypervisor to verify a token on your instance - not remotely in the same class)
But if the net effect is that one bug in a frontend can cause the server to tell the cert server to tell the secure enclave to tell the wire mesh protected crypto coprocessor to sign a bogus certificate then what are we really doing here.
We looked at various systems to manage intermediate ca issuance and reminders for renewal and the cost was incredible... most were >$200k!
Using scripts to automatically generate certificates and using the ugly but effective Windows CA web interface for "vanity" stuff does 90% of what those solutions do. I think we had an intern write a monitoring plugin to open tickets for soon to expire certificates and a few other things that covered the remaining 10%.