x/crypto/acme: support subproblems #38978
Closed
Projects
Milestone
Comments
Change https://golang.org/cl/233165 mentions this issue: |
/cc @FiloSottile @x1ddos |
Since this changes an API, marking it as a proposal. CL 233165 proposes the following API addition/change:
|
Based on the discussion above, this proposal seems like a likely accept. |
No change in consensus, so accepted. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
Called
AuthorizeOrder
to request a new ACMEv2 Order with identifiers rejected by the CAWhat did you expect to see?
An
acme.Error
populated with RFC 8555 subproblemsWhat did you see instead?
An
acme.Error
with no subproblems available.This limits the information clients can provide to users and prevents automated corrections to the invalid Order, such as by removing the the rejected identifiers and requesting a new Order.
The text was updated successfully, but these errors were encountered: