Continuing the discussion from ACME breaking change: Most GETs become POSTs : [image] ACME breaking change: Most GETs become POSTs During a final round of review at IETF, ACME received some feedback that is likely to lead to a breaking change in how ACME handles GETs. Please read my summary for d…

[image] rmbolger: Just curious if there is any news on this topic? We're going to be posting an API announcement in the next day or so. In the meantime here's a quick summary of my understanding of things (subject to change!): The POST-as-GET change met consensus and was merged into the dr…

[image] cpu: but I believe current consensus internally is leaning towards a flag day with the V2 API. I think this is going to lead to a lot of broken wildcard renewals because we have a lot of Certbot users who don't have regular client upgrades (which you can see in the server-side client …

[image] schoen: I think this is going to lead to a lot of broken wildcard renewals because we have a lot of Certbot users who don’t have regular client upgrades These users would experience the same breakage when the V2 API was removed in favour of V3. If we schedule the V2 API flag day with …

Thanks for the update, @cpu . So it sounds like the timeline for client devs adopting POST-as-GET (PaG) support should look something like this. Today Start working on a branch of your client that transitions to PaG using Pebble as the test server Date X when Staging supports PaG Verify branch …

This client implementation plan sounds sensible to me. I’d estimate that “Date X” is likely to be in the next week or two, with Date Y following a week afterwards.

Also just to clarify, do I have this right? The only resources that will continue to be available without PaG after November 1, 2019 are: Directory Forever GET’able newNonce Preferably HEAD, but also GET’able Certificates Though this is a Let’s Encrypt specific implementation decision based…

[image] rmbolger: The only resources that will continue to be available without PaG after November 1, 2019 are: Directory Forever GET’able newNonce Preferably HEAD, but also GET’able Both correct :white_check_mark: [image] rmbolger: Certificates Though this is a Let’s Encrypt s…

[image] cpu: I need to verify our plans here with @jsha and @roland . I believe our intention is to only suport POST-as-GET to certificates. The MAY allow you’re referring to was recently removed in the working copy of the draft . Yep, that's correct. We'll treat certificates the same way we t…

Any update on GETS -> POSTs conversation

Client dev

cpu October 9, 2018, 7:18pm 5

We've posted our API announcement outlining the plan for POST-as-GET support & deprecation of unauthenticated GETs for ACME v2.

We're targeting November 1st, 2019 for this.

Topic		Replies	Views
ACME breaking change: Most GETs become POSTs API Announcements	0	4583	August 30, 2018
ACME v2 - Scheduled deprecation of unauthenticated resource GETs API Announcements	4	31031	September 24, 2020
ACMEv2 - POST-as-GET on /acme/cert/? Client dev	2	1777	May 6, 2019
POST-as-GET and privacy Client dev	16	4121	January 31, 2020
ACME v2 API Staging Availability Issuance Tech	13	4070	January 9, 2018

Any update on GETS -> POSTs conversation

Related topics