auth.missing_credential
No credential was sent
| Type | https://mthds.ai/errors/auth.missing_credential |
| Family | auth: Credentials and permissions. |
| Domain | account: the account's owner acts |
| Retry | no: repeating the operation fails the same way |
| HTTP status | 401 |
| Raised as | a problem document, sent as the body of an HTTP response or kept in a run's record |
What it means
The route requires a credential, and the request carried none. How a runtime authenticates is implementation-defined; the protocol reserves a bearer-token slot, and GET /version needs no credential.
What to do
Configure the client with a credential for this runtime, such as a bearer token in the Authorization header, and send the request again.
Next steps
A problem carries the step aimed at whoever reads it: the first when its reader is the domain's actor, the account's owner, and the second for any other reader.
| Reader | Kind | Detail |
|---|---|---|
| The domain's actor | check_credentials |
Send the request with a credential this runtime accepts. |
| Any other reader | contact_owner |
Ask the account's owner for a credential this runtime accepts. |
Detail
The problem's detail is written from this template, filled with the occurrence's parameters:
This route needs a credential, and the request carried none.
Parameters
This code declares no parameters, so its problems carry no params.
See also
- The routes
- Error Registry, which describes the members of this page
- Error Codes, every code of the core registry