{% extends "_layout.html" %} {% set title = "DPoP nonce required" %} {% set status = "401 Unauthorized" %} {% set description = "The server requires a DPoP nonce and has just supplied one. Retry once with it." %} {% block main %}

The server requires a nonce in the DPoP proof and has just supplied one. The response carries WWW-Authenticate: DPoP error="use_dpop_nonce" and the nonce in a DPoP-Nonce header. A missing or stale nonce is always this, never invalid-dpop-proof.

What to do

  1. Sign a fresh proof carrying the nonce from DPoP-Nonce, and retry the request once.
  2. Keep one nonce per origin: the stream host’s nonce is not the API’s.

The body

HTTP/1.1 401 Unauthorized
WWW-Authenticate: DPoP error="use_dpop_nonce"
DPoP-Nonce: eyJ7S_zG.eyJH0-Z.HX4w-7v

{
  "type":     "https://sc.example.com/server-errors/dpop-nonce-required",
  "title":    "DPoP nonce required",
  "status":   401,
  "instance": "/v1/jobs",
  "trace_id": "4bf92f3577b34da6a3ce929d0e0e4736"
}

At the two OAuth endpoints

At POST /v1/auth/token and POST /v1/auth/device the same condition is answered in the OAuth shape: 400, {"error": "use_dpop_nonce"}, with the nonce in DPoP-Nonce. The client does the same thing.

{% include "_help.html" %}

What this is not

invalid-dpop-proof is a proof that failed a check: malformed, replayed, or signed by the wrong key. That one fails and is not retried, except once after correcting the clock for a proof refused for its time. This one is always retried once.

{% endblock %}