commit 45def97aa7b1113b423f56eea4692b4750e1e901
parent d6efa5a5bcb7420ea9cd887b04dffbbe69e573df
Author: Christian Grothoff <christian@grothoff.org>
Date: Thu, 6 Aug 2026 15:37:58 +0200
update challenger protocol spec for v8
Diffstat:
3 files changed, 7 insertions(+), 2 deletions(-)
diff --git a/core/challenger/get-info.rst b/core/challenger/get-info.rst
@@ -12,11 +12,12 @@
:http:statuscode:`200 OK`:
The body contains the address as a `ChallengerInfoResponse`.
- :http:statuscode:`403 Forbidden`:
- The bearer token is missing or invalid (malformed).
+ :http:statuscode:`401 Unauthorized`:
+ The bearer token is missing, invalid (malformed) or unknown.
:http:statuscode:`404 Not found`:
The bearer token is invalid (includes unknown or expired).
Returned with ``TALER_EC_CHALLENGER_GRANT_UNKNOWN``.
+ Removed in **v8** (to better match RFC 6750)
:http:statuscode:`500 Internal Server Error`:
The challenger service encountered an internal error,
typically a database failure. Usually returned with
diff --git a/core/challenger/post-solve-NONCE.rst b/core/challenger/post-solve-NONCE.rst
@@ -31,6 +31,9 @@
The service is unaware of a matching challenge.
The response will include error
code, hint and detail. Since protocol **v1**.
+ :http:statuscode:`409 Conflict`:
+ The service had never actually transmitted a TAN, so solving
+ is naturally impossible. Since protocol **v8**.
:http:statuscode:`429 Too Many Requests`:
There have been too many attempts to solve the challenge
for this address (and $NONCE). The user-agent should
diff --git a/core/challenger/post-token.rst b/core/challenger/post-token.rst
@@ -48,6 +48,7 @@
the user has not (yet) submitted any address, so the token
cannot be issued. Returned with
``TALER_EC_CHALLENGER_MISSING_ADDRESS``.
+ Removed in **v8** (to better match RFC 6749, section 5.2)
:http:statuscode:`500 Internal Server Error`:
The challenger service encountered an internal error,
for example a database failure or a failure of the SHA-256
