-
Notifications
You must be signed in to change notification settings - Fork 149
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement order "ready" state #98
Labels
Comments
cpu
added a commit
that referenced
this issue
May 22, 2018
This PR updates the way Pebble handles an Order's status field to closer match the way we handle it in Boulder. This means the order's status is considered to be a calculated field derived based on the order's error/beganProcessing/certificate fields and the status/expires/error of the order's associated authorizations. Along the way the new "Ready" status was implemented. This PR also addresses the problem of the order status not being updated when an authorization is failed. Now, an order has a problem details field that is set when an authorization associated with the order has a failed challenge validation. Resolves #110 and #98
Isn't this about the change described in https://community.letsencrypt.org/t/acmev2-order-ready-status/62866? If yes, is there a reason this issue is still open? |
@felixfontein No reason except that I forgot to close it! Thanks for the ping. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Per https://tools.ietf.org/html/draft-ietf-acme-acme-10#section-7.1.6
The text was updated successfully, but these errors were encountered: