Home / Acmefyer / Private CA

AcmefyerAgent-based Certificate Manager

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.

01By handWhat a CA of your own involves

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.
02With AcmefyerWhat the local CA takes care of

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.
03SetupSet up once, then it runs on its own
  1. 01

    Create the root CA

    With a name constraint on your internal domains. Or import an existing CA.

  2. 02

    Create an intermediate CA

    For TLS servers, and more for clients or S/MIME if needed.

  3. 03

    Roll out trust

    Bring the root CA into the trust stores by Group Policy or through the agents.

  4. 04

    Issue certificates

    Enter the names, assign targets. From now on Acmefyer renews and deploys by itself.

04FAQFrequently asked questions about a private CA

When do I need a CA of my own, and when is Let’s Encrypt enough?

Let’s Encrypt is enough for everything that has a name under your public domain, on the internal network too. See Let’s Encrypt for internal servers. You need a CA of your own for purely internal names such as server.company.local, for IP addresses and for client certificates, for example for 802.1X or VPN.

How do I revoke an internal certificate?

On the certificate’s page you choose “Revoke” and the reason. Acmefyer revokes every still valid issuance, signs the revocation list anew at once and, if you like, issues a new certificate right away and rolls it out. Acmefyer can also revoke a replaced certificate by itself after every renewal, once the new one has reached every target.

How do clients find the revocation list?

Every new certificate names the address of the revocation list. The Acmefyer server serves it there over HTTP, on a port of its own, 80 by default. It is best to use a DNS name of its own such as pki.example.internal, as the address is fixed in every certificate. Acmefyer reports when a list cannot be signed or runs out soon.

How do my systems trust the private CA?

The root CA has to be in the trust store. In a Windows domain this is done by Group Policy, on mobile devices by MDM. On systems with an Acmefyer agent the target “Trust store (CA)” enters it, on Windows and Linux. Clients do not need the intermediate CAs, because servers send them along in their chain.

We already have an internal CA. Do we have to start over?

No. Acmefyer takes over an existing root or intermediate CA together with its private key. The root CA can stay offline if you import only the intermediate CA with its key. Certificates your CA issued before come in several at once. From then on Acmefyer renews the server certificates among them itself. If your CA should keep issuing itself, import only the finished certificates and deploy them through the agents.

Is the local CA included in the free version?

No. The local CA, revocation and revocation lists included, needs a license. You can try all other features without a license key.