Admin forbidden

Identifiers

Field	Value
Type URI	https://echo.labstack.com/pro/problems/admin-forbidden
Code	admin_forbidden
HTTP status	403

HTTP status	English title
403	Forbidden

When it occurs

Middleware configured in Config.Middleware returned HTTP 403. The console keeps the status and does not show the middleware’s message.

Client handling

Ask the console’s administrator for access. Retrying with the same credentials gives the same result.

Example response

If your application installs a custom handler, the body may differ.

HTTP/1.1 403 Forbidden
Content-Type: application/problem+json
Cache-Control: no-store

{
  "code": "admin_forbidden",
  "detail": "",
  "status": 403,
  "title": "Forbidden",
  "type": "https://echo.labstack.com/pro/problems/admin-forbidden"
}

Server correction

Check why Config.Middleware returned 403. Grant only the access the operator needs.

Response fields

Admin console

• code (string, always): The stable code above.
• detail (string, always): The console always sends detail. It is often empty and never contains the underlying error.
• status (integer, always): The HTTP status of the response.
• title (string, always): The HTTP status text, such as Conflict, unless the panel supplies its own title.
• type (string, always): The exact type URI above.

Headers:

• Cache-Control (always): no-store. The console sends it on every problem response, along with its usual security headers.

Notes:

• Fields are written in alphabetical order.
• The console rewrites every 404 response to admin_not_found with an empty detail.

Related behavior

See the admin console for access checks, action IDs and audit failures.