> On Mar 12, 2018, at 7:39 PM, Alan Doherty wrote:
>
> I wouldn't be a fan
>
> At 19:02 12/03/2018 Monday, Azoff, Justin S wrote:
>> I've been investigating the possibility of offering an ACME compatible
>> endpoint for local users
>> to use to obtain certificates through our normal CA proce
>
>
> if the client is hardcoded for LE its not designed to be used with other
> acme services (so inappropriate to use with others)
> most acme clients aren't as its configurable on all I've used
Many ACME clients default to using the production Let's Encrypt directory
endpoint URL, but it is *v
I wouldn't be a fan
At 19:02 12/03/2018 Monday, Azoff, Justin S wrote:
>I've been investigating the possibility of offering an ACME compatible
>endpoint for local users
>to use to obtain certificates through our normal CA process. One of the
>issues I have identified
>is that if I were to run
I've been investigating the possibility of offering an ACME compatible endpoint
for local users
to use to obtain certificates through our normal CA process. One of the issues
I have identified
is that if I were to run a local ACME server, every client would have to be
configured to point at it.
