ACME accounts
Configure registrations against the 9 supported public CAs that speak ACME. Most are open registration; a few require External Account Binding (EAB).
Custom ACME CAs
Issue from any ACME server that is not in the public catalog โ step-ca, EJBCA, Vault PKI, or a commercial CA's ACME endpoint โ with its own CA certificate, network rule and External Account Binding.
Microsoft AD CS
Issue from your Active Directory Certificate Services CA โ directly over RPC (only the CA role is needed) or through the CES/CEP web services.
EAB-bound CAs
External Account Binding ties an ACME account to an existing customer record at the CA. This page tells you where the kid + HMAC come from for each EAB-required provider.
AD CS server setup (CES/CEP)
Windows-server-side preparation for CertAutoPilot's AD CS integration: install the CA + CES/CEP role services with username/password authentication, verify the IIS endpoints, create and publish an enrollment template, and set up a least-privilege service account.
CA connectors
Issue from a commercial CA through its own REST API instead of ACME โ a connection holds the vendor and its credential; CertAutoPilot validates the domain, places the order, writes any DNS validation record into your zone, polls until the certificate is issued and cleans up. Shipped vendor: GlobalSign Atlas.
GlobalSign Atlas
Issue GlobalSign certificates through the Atlas Certificate Management API: an API credential plus an mTLS client certificate made from a CSR CertAutoPilot generates, domain validation on the Atlas account (published in your zone when needed), and a new certificate for every renewal.