Important notice to ACME Client developers regarding ACME v1 deprecation

Client dev
1

Clients not compatible with ACME v2 will progressively disappear from https://letsencrypt.org/docs/client-options/ (They will be greyed out first, and then removed).
The objective is to points users only to ACME v2 clients as the ACME v1 API is deprecated and will be removed (End of Life Plan for ACMEv1)

If you are the developer of an ACME Client or library:

Related: https://github.com/letsencrypt/website/issues/557

8 Likes
5

Now live: https://letsencrypt.org/docs/client-options/ Clients without ACME v2 apprears in grey.

3 Likes
6

Hi,
I noticed that some clients listed in https://github.com/letsencrypt/website/blob/master/data/clients.json are not appearing on the HTML version of the list; in particular that affects the Ansible acme_certificate module (which I’m working on :slight_smile: ). I also checked some close to it in the list (“Certify The Web (Windows)”, “itr-acme-client PHP library”, “stonemax/acme2 PHP client”, …), they’re also not showing up. Is there something we need to do about it?

2 Likes
7

You’re right, some clients were apparently didn’t specify a category. I’ll see if I can fix that.

2 Likes
8

@felixf There is a PR to fix it: https://github.com/letsencrypt/website/pull/672 . I’ve listed your client “Ansible acme_certificate module” in the Python category. Your client was the only one where the category/library option was not obvious. Is that category fine with you or do you see one better suited?

2 Likes
9

If anyone else is interested: the category ended up being called Configuration management tools and the list should now be complete again.

3 Likes