Brings Let's Encrypt to LAN and other locked down environments.
This is a work in progress (unstable). Contributions are very welcome!
- A server instance is running somewhere in your network infrastructure, with network access to
your DNS provider of choice and the ACME directory you'll want to use (Let's Encrypt most likely).
The server is configured with the DNS names you control (e.g.somecompany.io
andother.co
). - Clients are deployed on the machines where you need the certificates for your applications.
- Certificates magically appear on the client machine in the directory you've configured.
LAN
+------------------------------------------------------------------------------------+
| |
| |
| |
| Server 1 |
| +--------------------------------------------+ |
| | | |
| | my-db.somecompany.io | |
| | app1.somecompany.io intercert (client) | |
| | app2.somecompany.io | +-----------------------+ |
| +--------------------------------------------+----------| | |
| | | |
| Server N | intercert (server) | |
| +--------------------------------------------+----------| | |
| | | +-----------------------+ |
| | redis.somecompany.io | / | |
| | intranet.other.co intercert (client) | / | |
| | | / | |
| +--------------------------------------------+ / | |
| / | |
+------------------------------------------------------/------------------------|----+
+------------------ +----------------|-+
| | | |
| DNS-provider | | ACME provider |
| | | |
+-----------------+ +------------------+
A huge thanks to these projects