Boulder: Non-string /directory entries cause some draft-01 ACME clients to break

[cpu]

As reported by @PovilasVytautasC there are ACME clients that assumed the /directory key value's are always strings and not objects. These clients break in the presence of the "meta" entry that was added in 65f1242ed47559624bfc1527646375da4405c591

The meta directory entry has been present in the ACME draft since draft-02 and we are taking steps to future-proof clients against making assumptions about the /directory for this reason I'm creating this issue mostly to document & discuss. I don't propose we remove the meta entry at this time.

[cpu]

One affected client - Certes, See https://github.com/fszlin/certes/issues/5

[cpu]

Another related community forum thread

[zr3]

Here is a pull request in Certes with a proposed fix: https://github.com/fszlin/certes/pull/6

[jsha]

This has now been live for a while and I think most clients have fixed the issue. Closing.