title: Using step-ca as an intermediate ca with certificates provided by a parent CA
body: <p>I am looking to use a intermediate CA which can sign certificates via ACME.  We have a number of internal web servers which are not accessable on the internet which use SSL all of which need to be managed manually.  We already have an internal CA where the CA authority is installed on all internal machines.  I was hoping to install step CA with a certificate provided from the existing authority which it can then use to sign certificates using ACME (all of the servers are in DNS and this DNS is managed internally, so a DNS name check is a valid check).</p>
  <p>I can get most of the way but it appears that set-ca always uses a self signed certificate for the ACME part of the service, so when certbot or whatever connects to the ACME service it just generates a certificate error because of the self signed one that it is using for the communications (even though it would ultimatly issue one which could be verified).</p>
  <p>Has anyone any experence in addressing this?  I could go and install the self signed cert on all the relevant servers, but this kind of nullifies the point of using ACME, if I have to go and manually update a certifiate every 6 months on a number of machines I might as well just keep with the current process.</p>