taler-docs

Documentation for GNU Taler components, APIs and protocols
Log | Files | Refs | README | LICENSE

commit 546a40d319677d0553c882605840e2e245402238
parent 16e98153257e1c9bd66aa9d861294aaba87991b6
Author: Christian Grothoff <grothoff@gnunet.org>
Date:   Sun, 19 Jul 2026 23:13:44 +0200

move ECs to corrected 400 status code

Diffstat:
Mcore/challenger/post-token.rst | 8++++----
1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/core/challenger/post-token.rst b/core/challenger/post-token.rst @@ -28,6 +28,9 @@ ``client_secret``, ``code`` or ``redirect_uri``) is missing or malformed, or ``grant_type`` is not ``authorization_code``. Usually returned with ``TALER_EC_GENERIC_PARAMETER_MISSING`` + ``TALER_EC_CHALLENGER_CLIENT_FORBIDDEN_BAD_CODE``, + ``TALER_EC_CHALLENGER_GENERIC_VALIDATION_UNKNOWN``, + ``TALER_EC_CHALLENGER_GRANT_UNKNOWN`` or ``TALER_EC_GENERIC_PARAMETER_MALFORMED``. :http:statuscode:`401 Unauthorized`: Authentication of the client failed. Returned (per @@ -38,10 +41,7 @@ ``code_verifier`` does not match the saved ``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``. + or ``TALER_EC_CHALLENGER_GENERIC_CLIENT_UNKNOWN``. PKCE-related rejections are since protocol **v3**. :http:statuscode:`409 Conflict`: A ``code`` was presented for a validation process for which