r/PKI

▲ 7 r/PKI

Please suggest for 1 tier CA

Hi Guys,

Please help a fellow pki newbie

Sooo, we currently have an on-prem Microsoft Tier 1 CA setup where a single server is acting as both Root CA and Issuing CA (yeah, not ideal, inherited setup).

We’re planning to migrate this CA infrastructure to AWS and I’m trying to understand the cleanest and safest approach from people who’ve already done similar migrations in production.

Current environment:

Windows ADCS

Single-tier CA (Root + Issuing on same server)

IIS is also hosting certificate-related applications/pages under Default Web Site

Existing certificates are actively being used internally and externally

We also have templates, CRL/AIA locations, and auto-enrollment in place

Some of the things I’m trying to figure out:

Is taking a normal CA backup enough? From what I understand, the CA backup only captures:

CA database

Private key

Registry configuration

But it won’t include IIS configuration/apps under Default Web Site. So for a proper migration, do I also need IIS backup/export ,App pool configs Website bindings,SSL bindings?

Please suggest

reddit.com
u/sadpumpkin1616 — 2 days ago
▲ 12 r/PKI

Whats recommended for the offline root, issuing intermediate CAs, and end entities that maximizes security without breaking legacy device and app compatibility?

I have seen EDCSA recommended over RSA, but won’t that break functionality in any environment that needs to maintain legacy compatibility?

reddit.com
u/Fabulous_Cow_4714 — 10 days ago
▲ 11 r/PKI+1 crossposts

The CA/Browser Forum's Ballot SC-081 is already in effect. 200-day max as of March 2026, 100 days in March 2027, 47 days in March 2029.

The math on renewal workload scales linearly: 50 certificates managed manually goes from ~50 renewals a year at 398 days to ~400 at 47 days. Same cert count, 8x the operations work.

Wrote up the canonical schedule and what it does to teams still running manual processes: https://www.certkit.io/blog/shrinking-certificate-lifetimes

certkit.io
u/certkit — 9 days ago
▲ 29 r/PKI

Heads up. Let's Encrypt paused all production + staging issuance while they investigate a potential incident.

Heads up. Let's Encrypt paused all production + staging issuance while they investigate a potential incident.

The TLDR:

  • New certs and renewals are failing right now
  • Existing certs are unaffected — your sites stay up
  • Turn off your retry loops. Rate limits will bite hard the second issuance resumes

Status page: https://letsencrypt.status.io/

LE flagged this as "potential" - they halt preemptively whenever something looks off, so this could clear in an hour or run longer.

u/certctl — 5 days ago
▲ 4 r/PKI+1 crossposts

Hey guys,

We have just duplicated the default Webserver cert template and added the CA manager approval required tick on the certificate template so the admins can request for the certificates with managers' approval.

Certificate request is going through fine but when user tries to retrieve the certificate, they are getting this error

Active Directory Certificate Services could not process request 2876 due to an error: Access is denied. 0x80070005 (WIN32: 5 ERROR_ACCESS_DENIED). Additional information: Error verifying access
Event ID : 22 under the Application log.

On the cert template permissions look like this,
Authenticated users : read and enroll
Domain computers : read and enroll

Upon looking at the security event logs,

  1. when the cert requests come through , the requestor is the computer account. as they are requesting the cert via certlm.msc console > Personal > request the cert
  2. after the CA manger approved the request, and when a user tries to request for the certificate, the requestor shows as their logged in user account on that computer they are requesting the certificate from.

Quick Fix that worked : [ is this the standard? ]

  1. I added their user account to Read & Request certificate on the CA Properties > Security tab, which allowed them to retrieve the certificate.

any guess, what am I missing here?
or
any configuration need to be altered?
and
what is the standard best practice when it comes to web server certificate that has SAN to be supplied in the request?

Thanks alot.

reddit.com
u/Top-Height4256 — 13 days ago
▲ 21 r/PKI

A month ago I posted certctl here and got useful feedback, especially around network-appliance deployment, intermediates and client cert key usage, and the lack of step-by-step guides. Some of that's been addressed, some is still open.

https://certctl.io

The biggest shift: certctl now ships three enrollment-protocol servers.

RFC 8555 ACME server with RFC 9773 ARI. cert-manager, certbot, lego, and acme.sh can issue against certctl directly. Two modes per certificate profile: trust_authenticated for east-west service-mesh certs, and challenge with full HTTP-01 / DNS-01 / TLS-ALPN-01 validation.

RFC 8894 SCEP server with native Microsoft Intune challenge dispatch and per-profile dispatch. ChromeOS, Intune, and per-fleet RA-cert plus challenge-password setups all supported on one endpoint.

RFC 7030 EST server for HTTPS-based PKCS#10 enrollment: 802.1X / Wi-Fi auth, MDM IoT, FreeRADIUS.

Multi-level CA hierarchy is now a first-class managed primitive.

Issuer connectors: 5 → 12. Added HashiCorp Vault PKI, AWS Private CA, Google CAS, DigiCert CertCentral, Sectigo, GlobalSign, EJBCA, and Entrust. ADCS still isn't shipped; a GitHub issue with your specific protocol mode would help prioritize it.

Target connectors: 3 → 15. Added Caddy, Traefik, Envoy, Postfix/Dovecot, Windows Cert Store, Java Keystore, Kubernetes Secrets, AWS ACM, Azure Key Vault, and SSH (agentless via SFTP). F5 BIG-IP via iControl REST is the first network-appliance target via the proxy-agent pattern. Palo Alto (PAN-OS XML), FortiGate (FortiOS REST), and Citrix ADC (NITRO REST) are next on the roadmap, all free V2 work under BSL.

Two-person approval for high-stakes issuance via profile-level RequiresApproval=true. Self-approval is refused.

HSM-ready signer abstraction. FileDriver shipped. PKCS#11, cloud KMS, and SSH-CA drivers slot in next.

Cloud discovery for AWS Secrets Manager, Azure Key Vault, and GCP Secret Manager. Plus existing agent filesystem scans and network CIDR scans.

Notifiers: 2 → 6 with Slack, Teams, PagerDuty, and OpsGenie added. Per-policy severity routing. Default expiry thresholds T-30 / T-14 / T-7 / T-0.

HTTPS-only control plane on TLS 1.3. Immutable audit trail.

License is still BSL 1.1, free to self-host, no paid tier. Auto-converts to Apache 2.0 in 2076.

Try it

 git clone https://github.com/certctl-io/certctl.git
 cd certctl && docker compose -f deploy/docker-compose.yml up -d
 open https://localhost:8443

Still alpha for production. Actively maintained, shipping weekly. Open an issue if something breaks.

u/certctl — 8 days ago