ACMEv2 orders list

[yourivw]

Hi everyone,

Since a few days, I’m developing a PHP class for ACMEv2. I’m stuck on the order list at the moment, and what I find in the documentation doesn’t work. When retrieving account information, as specified under https://github.com/ietf-wg-acme/acme/blob/master/draft-ietf-acme-acme.md#account-objects, no ‘orders’ is found in the JSON response:

HTTP/1.1 100 Continue Expires: Mon, 29 Jan 2018 15:48:51 GMT Cache-Control: max-age=0, no-cache, no-store Pragma: no-cache HTTP/1.1 200 OK Server: nginx Content-Type: application/json Content-Length: 992 Boulder-Requester: 5463387 Link: ;rel="terms-of-service" Replay-Nonce: ZaY…2uk X-Frame-Options: DENY Strict-Transport-Security: max-age=604800 Expires: Mon, 29 Jan 2018 15:48:52 GMT Cache-Control: max-age=0, no-cache, no-store Pragma: no-cache Date: Mon, 29 Jan 2018 15:48:52 GMT Connection: keep-alive

[id] => 5463387 
[key] => 
     [kty] => RSA 
     [n] => 2Iz…uWs 
     [e] => AQAB
[contact] => 
      mailto:test@test.com
[agreement] => https://letsencrypt.org/documents/LE-SA-v1.2-November-15-2017.pdf 
[initialIp] => 92.xxx.xxx.xxx
[createdAt] => 2018-01-29T13:12:45Z 
[status] => valid

What am I missing? I shortened the key and nonce for readability.

Thanks in advance!

[cpu]

Hi @yourivw,

We haven’t yet implemented the “orders” field of the account object. You should follow this Boulder issue: https://github.com/letsencrypt/boulder/issues/3335

This field is a convenience for finding an account’s existing order. We plan to implement it but it’s low priority. A client can maintain their own list of order IDs in the meantime.

Thanks!

[yourivw]

Hi,

Thank you for the quick reply. I had a look at the boulder github, but apparently I missed that particular issue…
I am planning on storing the orders myself, as you suggested. Nevertheless I do hope you implement this feature in the future.

Thanks!