9 Commits (80a6640103132db93fa8d45edf4c3f11a2f2533b)

Author	SHA1	Message	Date
max furman	80a6640103	[acme db interface] wip	3 years ago
max furman	1135ae04fc	[acme db interface] wip	3 years ago
max furman	03ba229bcb	[acme db interface] wip more errors	3 years ago
max furman	2ae43ef2dc	[acme db interface] wip errors	3 years ago
max furman	461bad3fef	[acme db interface] wip	3 years ago
David Cowden	a26b5f322d	acme/api: Brush up documentation on key-change ... Add more specific wording describing what a 501 means and add more color explaining how official vs unofficial error types should be handled.	4 years ago
David Cowden	b26e6e42b3	acme: Return 501 for the key-change route ... RFC 8555 § 7.3.5 is not listed as optional but we do not currently support it. Rather than 404, return a 501 to inform clients that this functionality is not yet implemented. The notImplmented error type is not an official error registered in the ietf:params:acme:error namespace, so prefix if with step:acme:error. An ACME server is allowed to return other errors and clients should display the message detail to users. Fixes: https://github.com/smallstep/certificates/issues/209	4 years ago
max furman	c255274572	Should be returning status code 400 for ACME Account Not Found. ... Issue #173	4 years ago
max furman	e3826dd1c3	Add ACME CA capabilities	5 years ago