taler-docs

commit f1fd027c473738f4a443ef9c5c9f2d066244f45f
parent 0b8ba06aa18ebb97ca52e80b3f84e82eb04d8471
Author: Christian Grothoff <christian@grothoff.org>
Date:   Thu,  6 Aug 2026 18:33:02 +0200

more EC clarifications

Diffstat:
M
core/challenger/get-info.rst
 | 
6
+++++-
M
core/challenger/post-token.rst
 | 
7
++++++-

2 files changed, 11 insertions(+), 2 deletions(-)
diff --git a/core/challenger/get-info.rst b/core/challenger/get-info.rst
@@ -28,8 +28,12 @@
     * ``TALER_EC_GENERIC_PARAMETER_MALFORMED`` --- the ``Authorization``
       header does not use the ``Bearer`` scheme (``error`` is
       ``invalid_request``, ``detail`` is ``"Authorization"``).
-    * ``TALER_EC_CHALLENGER_GRANT_UNKNOWN`` --- the token does not decode,
+    * ``TALER_EC_CHALLENGER_TOKEN_UNKNOWN`` --- the token does not decode,
       is unknown, or has expired (``error`` is ``invalid_token``).
+      Since protocol **v8**; previously
+      ``TALER_EC_CHALLENGER_GRANT_UNKNOWN``, which is now reserved for the
+      *authorization grant* at :http:post:`/token </token>` so that each
+      error code maps to exactly one HTTP status.
 
     .. note::
 
diff --git a/core/challenger/post-token.rst b/core/challenger/post-token.rst
@@ -74,7 +74,12 @@
     ``redirect_uri`` does not match the one registered with the client.
     Error codes used are:
 
-    * ``TALER_EC_CHALLENGER_GENERIC_CLIENT_UNKNOWN``
+    * ``TALER_EC_CHALLENGER_CLIENT_AUTHENTICATION_FAILED`` --- the
+      ``client_id``/``client_secret`` pair does not match a registered
+      client.  Since protocol **v8**; previously
+      ``TALER_EC_CHALLENGER_GENERIC_CLIENT_UNKNOWN``, which is now used
+      only by :http:post:`/setup/$CLIENT_ID </setup/$CLIENT_ID>` with a
+      ``404`` so that each error code maps to exactly one HTTP status.
     * ``TALER_EC_CHALLENGER_GENERIC_CLIENT_FORBIDDEN_BAD_REDIRECT_URI``
 
     Both are returned with ``error`` set to ``invalid_client`` and a