We have a mix of remote desktop farms, VPNs, IIS applications, and Exchange services. Manually issuing and installing certificates every few weeks does not seem workable. How are people handling renewal across different systems?
How are you planning for shorter SSL certificate lifetimes?
Answers
Start with ACME for the public certificates, but treat issuance and deployment as separate jobs. Getting a new certificate is not much help if it never gets installed on the VPN or bound to the right IIS site.
Inventory the certificates, where they are used, who controls domain validation, and how each service accepts updates. Then automate renewal and installation for one service type at a time. Add monitoring for expiry and failed deployments so a broken automation job doesn't quietly become an outage.
Reply to this answer
The domain ownership piece can be the hard part. If another department controls validation and takes days to process requests, an ACME client on your server won't fix that by itself.
Get the domain owner involved early and agree on a validation process that can run automatically. Without that coordination, shorter lifetimes just turn the existing approval queue into a more frequent problem.
Reply to this answer
Not every certificate needs to come from a public CA. For internal-only services, a private CA can be an option if the client devices can be configured to trust it. The shortened public certificate lifetime rules don't automatically apply to private CAs.
Private issuance can also be automated with ACME-capable CA software. You still have to manage client trust and get renewed certificates onto the services.
p.849~velcrospool:
That won't suit a service used by unmanaged clients unless those clients can be made to trust the private CA.
Reply to this answer
Expect some awkward integrations. A certificate management platform or ACME client may cover issuance, but each appliance and application can have a different installation process. Some need scripts or vendor-specific integration rather than a native ACME client.
I'd prioritize the systems with no reliable deployment method and check what their vendors support. That gives you time to find a workaround or consider replacing a product before manual renewals become unmanageable.
Reply to this answer
ACME doesn't mean you're locked into one certificate authority. There are public providers and private CA tools that support it, so check the options against your requirements rather than assuming every certificate has to come from the same place.
Reply to this answer
Add your answer
Answers are reviewed before publication.
7m+claspwinder_581:
Test replacement outside the normal renewal schedule too. A revocation or other urgent reissue is a good reason to know the deployment path works on demand.