While developing an ACME client using certbot’s python-acme, I realized that it is not ready to receive an “userActionRequired” error, since the class “Error” (on the file certbot/acme/acme/messages.py) would ignore the field “instance” described in the section 7.3.4 of the RFC (https://tools.ietf.org/html/draft-ietf-acme-acme-13#section-7.3.4), making it completely inaccessible for anyone using this library. Although not the perfect solution, but patching python-acme would fix it. The problem is that there is no where to test it against. I’m not a Go developer, but I don’t seem to find any implementation of the “userActionRequired” error anywhere in the Boulder server code.
Even though the instructions at the “instance” url are obscure and have to be followed by the user, I would like to have most features of my ACME client automated, but the “Changes of Terms of Service” seems to only exist in the RFC draft.
So the question is, how can it be tested? Is it going to be implemented in Boulder/certbot? Or am I missing something here?
Thank you in advance!