unauthorized: Missing or invalid owner token
The route needs the deployment's owner token as a Bearer token, and the request had none or a wrong one. On the multi-tenant hosted tier, the credential (an API key or a dashboard session) does not resolve to exactly one tenant.
The metrics route (GET /metrics) also answers 401 {"error": "unauthorized", "detail": "…"} without CORE_METRICS_TOKEN as a Bearer token; the owner token is not accepted there, and without CORE_METRICS_TOKEN configured the route is not served.
What to do
- Send
Authorization: Bearer $DYNAMO_OWNER_TOKEN. Never put the token on a command line or in a URL.
On the wire
HTTP 401, error type authentication_error.
{
"error": "invalid bearer token (fail closed)"
}
A request with no Authorization: Bearer … header (and no console or member session) receives {"error": "missing bearer token (fail closed)"}; a wrong token receives the body above. A front-door actor header that does not verify receives {"error": "invalid actor header (fail closed)"}. The metrics route's detail reads "GET /metrics needs CORE_METRICS_TOKEN".
On a single-tenant deployment the 401 body is the same with or without Dynamo-Error-Detail: 1: it carries no errorDetail, so nothing about the deployment is disclosed before authentication. The multi-tenant front door answers with error: "unauthorized" and an errorDetail whose message is "the credential does not resolve to exactly one tenant (fail closed)" and whose fix asks for one API key (dk_test_… or dk_live_…) as a Bearer token, or a dashboard sign-in.
See all error codes.