ACMEv2 Order "ready" Status


#1

As of Tuesday, June 19th the Staging ACMEv 2 endpoint returns Order objects with "status":"ready" when all of the order’s authorizations have "status" equal to "valid". As of Thursday, July 5th this change is also in effect for the production ACME v2 endpoint. This change has no bearing on ACME v1.

Please ensure your ACME v2 client does not error in the presence of this new order status value, or depend on order objects remaining in the “pending” status when all of the authorizations are status “valid”. We encourage ACME client developers to test their software’s support for the order “ready” status using Pebble, a small ACME v2 test server that already implements this change.

This change resolves one of the ACME v2 divergences mentioned in our initial ACME v2 announcement and brings Boulder/Let’s Encrypt in line with ACME draft-12 Section 7.1.6’s description of the order object status changes.

Thank you!

Edit: After feedback from client developers we have changed the initial staging release date from June 5th to June 19th and the production release date from June 21st to July 5th

Edit Updated to reflect that this is now live in staging

Edit_ Updated to reflect that this is now live in production_


Certbot 0.25.0 Release
Could not decode 'status' when performing a renew dry run
Can't Validate Certficiates
Deserialization error: Status not recognized
#2

Adding a comment to point out my last edit:

After feedback from client developers we have changed the initial staging release date from June 5th to June 19th and the production release date from June 21st to July 5th


#3

This change is now live in the staging environment.


#4

This change is now live in the production environment.


Need unblock IP