API "/directory" endpoint "meta" field addition


To remove one of Boulder’s divergences from the ACME spec we have recently added support for the “meta” directory element added described currently in ACME draft-07, Section 7.1.1.

This results in a new directory element with a non-string value that can contain additional CA specific metadata. Presently we are only including the “terms-of-service” meta key to help alleviate complexities of the early ACME drafts new-registration flow.

We have enabled this feature in Staging as of July 19th 2017 and in Production as of Thursday August 3rd. The new directory responses are of the form:

  "ajl589COTyk": "https://community.letsencrypt.org/t/adding-random-entries-to-the-directory/33417",
  "key-change": "https://acme-staging.api.letsencrypt.org/acme/key-change",
  "meta": {
    "terms-of-service": "https://letsencrypt.org/documents/LE-SA-v1.1.1-August-1-2016.pdf"
  "new-authz": "https://acme-staging.api.letsencrypt.org/acme/new-authz",
  "new-cert": "https://acme-staging.api.letsencrypt.org/acme/new-cert",
  "new-reg": "https://acme-staging.api.letsencrypt.org/acme/new-reg",
  "revoke-cert": "https://acme-staging.api.letsencrypt.org/acme/revoke-cert"

Note: The “ajl589COTyk” entry above will be different for each request. Please see the earlier API announcement about why we add random directory enries.

/directory endpoint changes on staging

Update: Edited the API Announcement to reflect that the “meta” Directory element is now enabled in Production.


Update two: Edited the API announcement to reflect that we have removed the flag from production until next week’s Boulder update.


Update three: Edited the API announcement to reflect that the meta element change is enabled in production again.