[GH-ISSUE #10] ACME v2 Compatibility #12

Closed
opened 2026-02-26 21:31:07 +03:00 by kerem · 1 comment
Owner

Originally created by @EmmanuelAtx on GitHub (Feb 20, 2018).
Original GitHub issue: https://github.com/ridercz/AutoACME/issues/10

Hi Ridercz,

We need wildcard certificates. Will you implement that?
https://community.letsencrypt.org/t/staging-endpoint-for-acme-v2/49605

Originally created by @EmmanuelAtx on GitHub (Feb 20, 2018). Original GitHub issue: https://github.com/ridercz/AutoACME/issues/10 Hi Ridercz, We need wildcard certificates. Will you implement that? https://community.letsencrypt.org/t/staging-endpoint-for-acme-v2/49605
kerem closed this issue 2026-02-26 21:31:08 +03:00
Author
Owner

@ridercz commented on GitHub (Feb 20, 2018):

Not in the foreseeable future.

According to the announcement, it would require DNS authorization, which is waaaaay out of scope for AutoACME. In fact, AutoACME was built explicitly for avoiding DNS authorization.

They "may explore additional validation options over time". If they'll do some form of HTTP-based authorization, I'll try to implement that.

<!-- gh-comment-id:367091643 --> @ridercz commented on GitHub (Feb 20, 2018): Not in the foreseeable future. According to the [announcement](https://letsencrypt.org/2017/07/06/wildcard-certificates-coming-jan-2018.html), it would require DNS authorization, which is waaaaay out of scope for AutoACME. In fact, AutoACME was built explicitly for avoiding DNS authorization. They _"may explore additional validation options over time"_. If they'll do some form of HTTP-based authorization, I'll try to implement that.
Sign in to join this conversation.
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/AutoACME#12
No description provided.