smallstep-certificates

Commit Graph

Author	SHA1	Message	Date
max furman	80a6640103	[acme db interface] wip	3 years ago
max furman	55bf5a4526	Add cert logging for acme/certificate api	4 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	e1409349f3	Allow relative URL for all links in ACME api ... * Pass the request context all the way down the ACME stack. * Save baseURL in context and use when generating ACME urls.	4 years ago
Clive Jevons	639993bd09	Read host and protocol information from request for links When constructing links we want to read the required host and protocol information in a dynamic manner from the request for constructing ACME links such as the directory information. This way, if the server is running behind a proxy, and we don't know what the exposed URL should be at runtime, we can construct the required information from the host, tls and X-Forwarded-Proto fields in the HTTP request. Inspired by the LetsEncrypt Boulder project (web/relative.go).	4 years ago
max furman	d368791606	Add x5c provisioner capabilities	5 years ago
max furman	e3826dd1c3	Add ACME CA capabilities	5 years ago

8 Commits (80a6640103132db93fa8d45edf4c3f11a2f2533b)