ACME: Certificate management has never been easier
summary
ACME automates certificate issuance using an account keypair to sign requests and challenge-response (HTTP or DNS) validation, with certificates issued by Let's Encrypt that are valid for 90 days (renew every 60 days). A Java ACME client SPI is integrated into WildFly Eletron, letting CLI commands create an ACME account, store keys in a keystore alias, obtain a cert, and reinitialize the key manager; renewal is identical to issuance and is automatable via a cron job.
AI-written summary · about
chapters (13)
- 0:00Start
- 0:24Overview
- 0:52Self-signed vs. Signed Certificates
- 3:12Traditional Certificate Management
- 5:57Introducing the ACME protocol
- 8:04Creating an account
- 9:15Requesting a certificate
- 11:37Renewing a certificate
- 11:56ACME protocol advantages
- 12:23ACME server implementations
- 12:58ACME client implementations
- 13:28A Java ACME client SPI
- 20:48Summary
related talks
25mSSL All The Things
39mA Walk Through the Land of
26mSSL all the things
45mLet's Encrypt ActiveMQ and Karaf!
30mCert-Manager Beyond Ingress – Exploring the Variety of Use Cases
11mACME TLS-SNI-01 issuing Let's Encrypt SSL-certs for any domain using shared hosting
15mCertificates in Kubernetes
26mcert-manager - Past, Present and Future