The LetsEncrypt Proxy does not interfere with any of the communication between the client and LetsEncrypt services, allowing you to utilise whichever LetsEncrypt client implementation you desire. In addition, by proxying all traffic through our service, you can ensure that all outbound LetsEncrypt traffic is managed and easily auditable through your network.
The vide shows an example Linux server requesting a LetsEncrypt certificate, the creation of the DNS TXT record that LetsEncrypt requires, and the resultant certificate shown in Jellyfish. Behind the scenes, the issued certificate is simply captured by our proxy service and sent over to Jellyfish, all without interfering with the client/server issuance process.
The process uses a few lines of commands which could be combined into server build and configure scripts to automatically enrol and configure certificates for webservers and other services running on Linux. The first part of the video is showing a low privilege user logging into Jellyfish then requesting a SCEP certificate for their Linux machine. The video then shows a high-privilege user logging in and viewing then approving the users request. The original user that requested the certificate is then sent instructions on how to request a certificate on their Linux box. The second part of the video shows a user requesting a certificate using the instructions sent to them. This also shows a full data dump of the certificate.
Automatic Enrolment Module | CogAE-ACME
Automatic Enrolment Module | Cog-AE Groups