2
Let's Encrypt API
Idea shared by echoDreamz - 12/13/2023 at 2:56 PM
Proposed
I see it is possible to disable LE for a domain, could the API be updated to allow enabling LE for a specific domain rather than doing a all-or-nothing situation. Some of our customers have their own certs, which the SM API has an option to allow for uploading certs, but not one that I can see for enabling for a domain.

5 Replies

Reply to Thread
0
+1
Gabriele Maoret - Head of SysAdmins at SERSIS Currently manages 6 SmarterMail installations (1 in the cloud for SERSIS which provides services to a few hundred third-party email domains + 5 on-premise for customers who prefer to have their mail server in-house)
1
Kyle Kerst Replied
Employee Post
I'm going to get a request escalated to have this looked at by development for you!
Kyle Kerst System/Network Administrator SmarterTools Inc. (877) 357-6278 www.smartertools.com
1
Awesome! SM doing certs on it's own is awesome, but not all customers want LE or have their own certs as well, we'd like to control SSL more from our control panel, so an API call to enable LE on a specific domain would be awesome.
0
Actually... as I typed that, I realized, the upload certificate API call could technically do what we want if we generate the LE cert ourselves and pass in the PFX to the upload call, does SM set IIS bindings on the upload certificate call or is it strictly just adding the PFX file to the centralized store?
0
Grady Werner Replied
Employee Post
Uploaded certs do not automatically add bindings. 

Also note that it will not generate auto certs for any host names that already fall into a matching certificate in the folder.  So basically by uploading one, you are “disabling” let’s encrypt for all host names that cert covers. 

Once those certs get within 20 days of expiring, however, it will start to request new ones. 
Grady Werner SmarterTools Inc. www.smartertools.com

Reply to Thread