Is the error that currently presents when I attempt a new registration via the v1 API’s staging endpoint the same error that will present from the production endpoint as of the 31st of this month?
Specifically, will the
type always be
urn:acme:error:unauthorized for this error?
The error is controlled by a feature flag in Boulder’s legacy web front end and we don’t intend to adjust the implementation between now and the production deprecation.
Hope that helps,
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.