Bring development closer to production with valid HTTPS certificates
summary
Demonstrates automating trusted TLS for local dev by running open-source step-ca, running `step ca init`, installing the generated root into the system trust store, starting the CA server, and requesting a cert for a Node.js site which produces server.crt/server.key files. The process takes fewer than five commands, yields a browser-trusted localhost HTTPS endpoint, and also supports internal services like Kubernetes and MySQL so dev/prod parity is preserved without browser errors.
AI-written summary · about
chapters (8)
- 0:00Introduction and speaker background
- 0:48Dev-prod parity and HTTPS necessity
- 2:11Limitations of localhost HTTPS
- 3:56How TLS certificates enable HTTPS
- 9:43Certificate authorities for local environments
- 11:56Step CA setup in five steps
- 13:07Demo walkthrough with Step CA
- 19:17Resources and conclusion
related talks
52mDeveloping with HTTPS in Containers
42mLet's go HTTPS
04mEasy, Local, & Self-Signed; Certificates for Ember Serve
30mHow Secure Is Your Build/Server?
42mEnterprise-wide SSL Automation w/Lemur + CloudCA
11mACME TLS-SNI-01 issuing Let's Encrypt SSL-certs for any domain using shared hosting
13mLet's Encrypt or how to make your site HTTPS
30mCert-Manager Beyond Ingress – Exploring the Variety of Use Cases