A private CA, with revocation list and automatic renewal.
No public certificate authority issues a certificate for names such as server.company.local or for private IP addresses. That takes a CA of your own. Acmefyer brings one: create root and intermediate CAs, issue certificates, renew them in time, deploy them via agent and revoke them through a revocation list (CRL) when needed.
An internal CA by hand: quick to create, tedious to run.
A root CA and a first server certificate take two lines with OpenSSL:
openssl req -x509 -newkey rsa:4096 -days 3650 -keyout ca.key -out ca.crt -subj "/CN=Example Internal Root CA"
openssl x509 -req -in server.csr -CA ca.crt -CAkey ca.key -CAcreateserial -days 397 -extfile san.cnf -out server.crt
The work starts afterwards. Someone has to know which certificate expires when, issue it anew and bring it to the server. The CA’s key sits in a file. And to revoke a certificate, a revocation list is needed that is signed, published and renewed in time.
- Renewal
- Internal certificates expire just like public ones. Without an overview nobody notices until a service is down.
- Distribution
- Every new certificate has to reach its target system, and the root CA the trust store of every client and server.
- Revocation
- Without a revocation list a certificate stays valid until it expires, even when its key has fallen into the wrong hands.
- Scope
- A CA without a name constraint can issue for any name, including ones that are not yours. Its key is accordingly sensitive.
Issue, renew, deploy and revoke internal certificates.
In Acmefyer you create a root CA, restricted to your internal domains if you like, plus intermediate CAs per purpose. Their certificates appear next to those from Let’s Encrypt in the same list and get the same targets: an agent installs them in IIS, NGINX, Tomcat or the Windows certificate store.
Before expiry Acmefyer issues every certificate anew with a new key and rolls it out through all targets again. The CA keys are stored encrypted in the database. The local CA is part of the license and not included in the free version.
- Root CA
- Lifetime up to 10 years, with a name constraint on your internal domains if you like. It signs intermediate CAs only.
- Intermediate CAs
- One per purpose: TLS server, TLS client (devices, users, 802.1X, VPN), email (S/MIME) or code signing.
- Certificates
- DNS names, wildcards too, IP addresses or email addresses. For TLS servers at most 825 days, with 397 being usual.
- Revocation list (CRL)
- Every CA signs its revocation list, and the server serves it over HTTP, on port 80 by default. The list of an intermediate CA is signed anew daily and at once after every revocation. There is no OCSP.
- Trust
- You roll out the root CA by Group Policy or MDM, or with the target “Trust store (CA)” through the agents on Windows and Linux.
- Existing CA
- Acmefyer takes over an existing root or intermediate CA together with its key, for example from XCA, OpenSSL or AD CS. Your systems then trust it already.
- 01
Create the root CA
With a name constraint on your internal domains. Or import an existing CA.
- 02
Create an intermediate CA
For TLS servers, and more for clients or S/MIME if needed.
- 03
Roll out trust
Bring the root CA into the trust stores by Group Policy or through the agents.
- 04
Issue certificates
Enter the names, assign targets. From now on Acmefyer renews and deploys by itself.
