in acme v1, i was able to get the expiry of a certificate off the response headers to
under acme v2 - and testing against pebble - i see the following:
- ‘finalize’ endpoint to an order has an “expires”
- the order status endpoint has an “expires” (the endpoint being a new-order’s headers’ “Location”)
after a lot of testing, these seem to be 1 second off from the “expires” encoded in the certificate itself.
should i just be parsing the signed certificate?