unknown_org

Docs version v1 (main) · Nauthera is pre-1.0, in a design-partner program

The path's /orgs/{slug} names no organization served there (404).

#Meaning

The organization router answers this for /orgs/{slug}/... when no organization holds the slug, and when the slug is the main organization's, which is served only at the server root.

#Impact

Every request of a client configured with the wrong issuer fails: its discovery, authorize and token calls all answer 404. It is a configuration error.

#Diagnosis

1. Compare the client's issuer with the organization's issuer as the admin API or dashboard shows it.
2. Refusals are recorded as organization.route.attempted with cause unknown_organization or main_organization_prefixed, coalesced per caller and slug.

#Mitigation

• As a client developer: use the issuer from the organization's discovery document; for the main organization, drop the /orgs/{slug} prefix.
• As an operator: confirm the organization exists and its slug is spelled as the client uses it.

#Escalation

Escalate when an existing organization's slug answers 404. Open an issue with the request id, the slug and the server version.

Problem code runbooks · Generated from internal/runbook/problems.yaml in nauthera-server.