Skip to content

The v1 docs follow nauthera-server's main branch and its 0.x releases on the way to 1.0, so fields and APIs can still change.

v1

invalid_authorization_details

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

The authorization_details parameter is malformed or names a type the client may not request (RFC 9396 §5).

Meaning

Sent by /authorize (redirected to the client) and /par when authorization_details is not a non-empty JSON array of well-formed objects, or names a type the client is not registered for. No registration path sets a client's authorization details types today, so every request that carries authorization_details is refused.

Impact

Rich authorization requests are not usable on this server yet. The user is returned to the application before any sign-in screen.

Diagnosis

The audit record under oauth.authorization.requested has reason invalid_authorization_details and cause authorization_details_malformed or authorization_details_type_not_registered.

Mitigation

  • As a client developer: omit authorization_details and express access with scopes and resource.
  • As an operator: nothing can be configured to allow it yet.
  • As a user: tell the application's owner.

Escalation

If you need rich authorization requests, raise a feature request rather than an incident.

OAuth error runbooks · Generated from internal/runbook/oauth.yaml in nauthera-server.