Currently when the Auth CLI creates a new certificate, it adds it directly to the disk store. This means that the Auth server is unaware of the certificate until the daemon is restarted, resulting in much confusion among users!
Instead, the CLI should wrap the ZMQ API so that it is published as soon as it's created. If this fails, it can fall back to the current behaviour with a warning that it couldn't connect to the API:
WARNING: Could not connect to the API to register this certificate, which either means that the Auth daemon is not running, or there's a connectivity issue. If the daemon is running, please restart it to register this certificate.
Currently when the Auth CLI creates a new certificate, it adds it directly to the disk store. This means that the Auth server is unaware of the certificate until the daemon is restarted, resulting in much confusion among users!
Instead, the CLI should wrap the ZMQ API so that it is published as soon as it's created. If this fails, it can fall back to the current behaviour with a warning that it couldn't connect to the API: