Authentication and authorization

Mon, 01 Jan 0001 00:00:00 +0000

The auth package authenticates and authorizes the requests a humus service serves, over HTTP and gRPC alike. A scheme is a typed value whose verify function turns a request’s credential into the end user’s own principal, which a handler reads back with the scheme’s From. A requirement is what a request must have: a scheme, a scheme with scopes, several schemes, or nothing at all. Three places enforce requirements, one for each way humus serves requests: openapi.Security for an OpenAPI API, auth.NewHandler for a plain http.Handler served by httpserver, and grpcauth’s Interceptors for a grpcserver Service.

Failure injection

Mon, 01 Jan 0001 00:00:00 +0000

Failure injection lets one request fail on purpose, in production or in a test, without failing anyone else’s. A request carries a failure scenario in its OpenTelemetry baggage, and every injection point the request passes through, such as a call to a dependency, looks itself up in the scenario and learns whether to fail or slow down. The end user then sees how the whole service copes with a dependency that is down or slow: its retries, its breakers and its fallbacks.

Hardening on Humus

Authentication and authorization

Failure injection