#37 Investigate ACME client implementation
Closed: wontfix 2 months ago by rcritten. Opened 9 years ago by ftweedal.

The Automatic Certificate Management Environment (ACME) protocol has been proposed by the letsencrypt initiative as a standard protocol for domain validation and certificate issuance. The overview from the spec[1]:

ACME allows a client to request certificate management actions using
a set of JSON messages carried over HTTPS. It is a prerequisite for
this process that the client be configured with the HTTPS URI for the
server. ACME messages MUST NOT be carried over "plain" HTTP, without
HTTPS semantics.

[1] ​https://raw.githubusercontent.com/letsencrypt/acme-spec/master/draft-barnes-acme.txt

Implementation of what would be required to enhance Certmonger to function
as an ACME client should be undertaken.


New milestone was created for milestone-less tickets.

Metadata Update from @mkosek:
- Issue set to the milestone: 0.0 NEEDS_TRIAGE

7 years ago

We should close this. There are many other ACME client solutions for a variety of use cases, including some well supported, actively developed and widely used solutions. It would be better to choose one of these than to implement ACME support in Certmonger.

Metadata Update from @ftweedal:
- Issue close_status updated to: None

2 months ago

Metadata Update from @rcritten:
- Issue close_status updated to: wontfix
- Issue status updated to: Closed (was: Open)

2 months ago

Login to comment on this ticket.

Metadata