Skip to main content

No principal

typehttps://docs.frem.sh/reference/api/errors/no-principal
HTTP status403 Forbidden

What it means

The request authenticated, but the calling user could not be resolved to a Forgejo account — so there is no identity to check ownership against.

The API refuses here rather than guessing an owner. A resource attributed to the wrong user id is a resource its real owner cannot see, which is a worse outcome than a clear refusal.

Example detail messages returned with this error:

  • Could not resolve the calling user.

What to do

Usually a token whose user has since been renamed or removed. Re-run fremforge auth login; if it persists, email support@frem.sh with the token id from fremforge auth tokens list — never the token itself.

Response shape

All fremforge API errors are RFC 9457 problem+json:

{
  "type": "https://docs.frem.sh/reference/api/errors/no-principal",
  "title": "Forbidden",
  "status": 403,
  "detail": "..."
}

Branch on type, not on title or detail - those are human-readable and may be reworded.

No findingsNo rewrites