unauthenticated

HTTP 401   title: Not authenticated

What it means

The access token or its DPoP proof was missing, invalid or expired, the token was issued by a different issuer or revoked, or a client assertion failed on POST <endpoint>/auth/claim or POST <endpoint>/auth/rotate. Every operation except schema needs an access token.

What to do next

Read detail: it says what to fix. For a token, ask POST <endpoint>/oauth/token with the client_credentials grant, a new client assertion that your registered key signs (aud is the origin you dialed) and a DPoP proof (see Registration and tokens). Then send the call again with Authorization: DPoP <access_token> and a new DPoP proof.

The response

{
  "type":   "https://kiosk.tech/problems/unauthenticated",
  "title":  "Not authenticated",
  "status": 401,
  "detail": "… what went wrong on THIS request …",
  "code":   "unauthenticated"
}

This page documents the RFC 9457 type URI https://kiosk.tech/problems/unauthenticated. The URI is an identifier, not a locator a client should fetch: branch on the document’s code member. The normative definition lives in the error vocabulary of the Kiosk specification (§9 of the formal spec).