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

Pushed Authorization Request (RFC 9126)

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

POST/par

Accepts the authorization-request parameters directly from a client-authenticated back channel and returns a single-use request_uri the client then passes to /authorize. Hardens the flow against request tampering and oversized front-channel requests. request_uri MUST NOT be present in the PAR body.

  • The access token, as Bearer <token> (RFC 6750 §2.1) or, for a sender-constrained token, DPoP <token> (RFC 9449 §7.1). A token minted with a cnf.jkt confirmation is only accepted together with a DPoP proof signed by that key, whichever of the two schemes carries it.

  • DPoPstring

    DPoP proof JWT (RFC 9449 §4). REQUIRED on a request presenting a DPoP-bound access token, and it must be signed by the key named in the token's cnf.jkt and cover this request's method and URI. The proof is read from the request itself rather than from this decoded parameter, so every protected operation is covered whether or not it declares it.

Request body

application/x-www-form-urlencoded

Authorization-request parameters pushed to the PAR endpoint (RFC 9126). Mirrors the /authorize query parameters plus client authentication.

  • MUST NOT be sent; present only so the server can reject it.

    at most 512 characters

  • Example"code"

    at most 64 characters

  • max_ageinteger · int64

    at least 0

  • client_idstring
    Example"nauthera_2Rk9"

    1–256 characters · pattern ^[!-~]+$

  • redirect_uristring · uri
    Example"https://app.example.com/callback"

    at most 2048 characters

  • scopestring
    Example"openid profile email"

    at most 2048 characters · pattern ^\S+( \S+)*$

  • statestring

    at most 1024 characters

  • noncestring

    at most 1024 characters

  • at most 64 characters

  • promptstring

    at most 64 characters · pattern ^(none|login|consent|select_account)( (none|login|consent|select_account))*$

  • at most 512 characters

  • at most 256 characters · pattern ^\S+( \S+)*$

  • at most 512 characters · pattern ^\S+( \S+)*$

  • claimsstring

    at most 8192 characters

  • 43–128 characters · pattern ^[A-Za-z0-9_-]+$

  • at most 64 characters

  • requeststring

    at most 16384 characters

  • at most 8192 characters

  • resourcestring · uri

    at most 2048 characters

  • dpop_jktstring

    exactly 43 characters · pattern ^[A-Za-z0-9_-]+$

  • at most 512 characters

  • Example"urn:ietf:params:oauth:client-assertion-type:jwt-bearer"

    at most 128 characters

  • at most 16384 characters

  • 201 Createdapplication/jsonThe pushed request was accepted.

    The pushed request was accepted.

    Headers

    • Cache-Controlno-store

    Body

    A pushed authorization request reference (RFC 9126 §2.2).

    • request_uristringrequired

      Single-use reference passed to /authorize.

      Example"urn:ietf:params:oauth:request_uri:6esc_11ACC5bwc014ltc14eY22c"
    • expires_inintegerrequired

      Lifetime of the request_uri in seconds.

      Example90
  • 429 Too Many Requestsapplication/problem+jsonToo many requests.

    Too many requests.

    Body

    RFC 9457 (formerly RFC 7807) problem details (application/problem+json). code is a stable machine-readable slug for the problem kind (it mirrors the last path segment of type), so consumers can branch on it without parsing prose. type is https://nauthera.io/problems/<code>, which resolves to the code's runbook: why it happened, who is affected and what to do (RFC 9457 §3.1.1). A problem without a code has about:blank. errors is present on validation failures and lists every offending field.

    • titlestringrequired
      Example"Request validation failed"
    • statusintegerrequired
      Example400
    • typestring · uri
      Example"https://nauthera.io/problems/validation_error"
    • detailstring
      Example"One or more fields did not satisfy the API schema."
    • codeenum

      The kind of problem, as a stable machine-readable slug a client branches on and translates rather than parsing title or detail, which are English prose for logs. A problem whose status says everything the server knows carries no code.

      Show more

      validation_error is the one code whose message is not a sentence about the code itself: the request failed the schema, and the specifics are the errors list — one entry per offending field — which a form renders on those fields. required and malformed are spelled like two of the per-field violation codes (FieldError.code) but mean something else; the two vocabularies are told apart by position, never by spelling.

      Compatibility: this is a CLOSED enum, with the same cost as AuditAction: a client generated against an older version of this document rejects a problem carrying a code added after it was built. Regenerate on upgrade, or decode the field as a plain string. It is enumerated anyway so that what a client must translate is knowable from the contract alone.

      Possible values43 values
      • invalid_request
      • invalid_credentials
      • forbidden
      • unauthorized
      • insufficient_user_authentication
      • protected_account
      • password_held_by_directory
      • last_role_administrator
      • invalid_code
      • too_many_requests
      • too_many_attempts
      • account_locked
      • account_unavailable
      • already_enrolled
      • registration_disabled
      • registration_conflict
      • captcha_failed
      • invalid_reset_link
      • password_reused
      • password_too_short
      • password_too_long
      • password_compromised
      • invalid_verification_link
      • invalid_invitation_link
      • mail_relay_missing
      • email_unverified
      • not_found
      • conflict
      • unavailable
      • busy
      • window_too_large
      • too_many_series
      • internal_error
      • rate_limited
      • malformed
      • body_too_large
      • required
      • validation_error
      • unknown_org
      • invalid_token
      • invalid_dpop_proof
      • use_dpop_nonce
      • server_error
    • instancestring
      Example"/introspect"
    • Example"8d94ed49-1caf-4ab3-9594-557142f2d023"
    • trace_idstring

      Distributed-trace id (hex) for correlating this response with traces and logs. Present only when tracing is enabled and the request was recorded. Opaque and safe to log/share.

      Example"4bf92f3577b34da6a3ce929d0e0e4736"
    • errorsarray of objects

      Field-level violations (present for validation errors).

      Each item:

      A single field-level validation violation.

      Show item attributes
      • fieldstringrequired

        Offending field, dotted for nested bodies (e.g. child.id).

        Example"token_type_hint"
      • codestringrequired

        Machine-readable violation code: required, too_short, too_long, pattern, invalid_format, not_allowed, minimum, maximum, multiple_of, too_few, too_many, not_unique, malformed.

        Example"not_allowed"
      • messagestringrequired
        Example"field token_type_hint must be one of [access_token, refresh_token]"
  • Errorapplication/jsonOAuth2 error response (RFC 6749 §5.2).

    OAuth2 error response (RFC 6749 §5.2).

    Headers

    • Cache-Controlno-store
    • WWW-Authenticatestring
    • DPoP-Noncestring

    Body

    An OAuth2 error response (RFC 6749 §5.2). iss (RFC 9207) is present on authorization-endpoint error responses so clients can detect mix-up.

    • errorstringrequired

      A single ASCII error code.

      Example"invalid_request"
    • Example"client_id, redirect_uri and response_type are required"
    • error_uristring · uri

      The error code's runbook (RFC 6749 §5.2): https://nauthera.io/runbooks/oauth/<error>.

      Example"https://nauthera.io/runbooks/oauth/invalid_request"
    • statestring

      Echoed authorization-request state (RFC 6749 §4.1.2.1).

    • issstring · uri

      Issuer identifier on authorization error responses (RFC 9207).