challenger

OAuth 2.0-based authentication service that validates user can receive messages at a certain address
Log | Files | Refs | Submodules | README | LICENSE

commit 93194d9661efbd50661c57b1ba5338481aac5942
parent d1f31b51c3b486b8bef9d3081207dadfa77f61bb
Author: Sebastian <sebasjm@gmail.com>
Date:   Tue,  2 Jul 2024 09:38:09 -0300

remove 428 which is not documented and the normal response gives enough info to the client

Diffstat:
Msrc/challenger/challenger-httpd_authorize.c | 14--------------
1 file changed, 0 insertions(+), 14 deletions(-)

diff --git a/src/challenger/challenger-httpd_authorize.c b/src/challenger/challenger-httpd_authorize.c @@ -232,20 +232,6 @@ CH_handler_authorize (struct CH_HandlerContext *hc, case GNUNET_DB_STATUS_SUCCESS_ONE_RESULT: break; } - if ( (0 == address_attempts_left) && - (0 == pin_transmissions_left) && - (0 == auth_attempts_left) ) - { - GNUNET_log (GNUNET_ERROR_TYPE_WARNING, - "Refusing authorization: zero attempts left\n"); - json_decref (last_address); - return reply_error (hc, - "unauthorized_client", - MHD_HTTP_TOO_MANY_REQUESTS, - TALER_EC_CHALLENGER_TOO_MANY_ATTEMPTS, - "client exceeded authorization attempts limit (too many addresses)"); - - } { enum GNUNET_GenericReturnValue ret; json_t *args;