commit 0a10558ad7e600eebe43dfdcc6ddef0da6ac6ece
parent 6f3adf89d534a7753ba43318174a1dec361cad77
Author: Christian Grothoff <grothoff@gnunet.org>
Date: Thu, 9 Jul 2026 20:52:59 +0200
adjust spec to match RFC status codes better
Diffstat:
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/core/challenger/post-token.rst b/core/challenger/post-token.rst
@@ -39,13 +39,10 @@
``code_challenge``. Returned with
``TALER_EC_CHALLENGER_GENERIC_CLIENT_FORBIDDEN_BAD_REDIRECT_URI``,
``TALER_EC_CHALLENGER_CLIENT_FORBIDDEN_BAD_CODE``,
+ ``TALER_EC_CHALLENGER_GENERIC_CLIENT_UNKNOWN``,
``TALER_EC_CHALLENGER_GENERIC_VALIDATION_UNKNOWN`` or
``TALER_EC_CHALLENGER_GRANT_UNKNOWN``.
PKCE-related rejections are since protocol **v3**.
- :http:statuscode:`404 Not found`:
- The service is unaware of a matching login process or client.
- Returned with error codes of
- ``TALER_EC_CHALLENGER_GENERIC_CLIENT_UNKNOWN``
:http:statuscode:`409 Conflict`:
A ``code`` was presented for a validation process for which
the user has not (yet) submitted any address, so the token
