challenger

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

commit e23d3ceeda8810ad21d3d1d23566811d9be7cc6d
parent 35caab4eec4cd11816acc9a49defe3df3c475c91
Author: Christian Grothoff <christian@grothoff.org>
Date:   Wed, 14 Feb 2024 10:59:57 +0100

-more logging

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

diff --git a/src/challenger/challenger-httpd_authorize.c b/src/challenger/challenger-httpd_authorize.c @@ -163,6 +163,10 @@ CH_handler_authorize (struct CH_HandlerContext *hc, return MHD_NO; case GNUNET_DB_STATUS_SUCCESS_NO_RESULTS: GNUNET_break_op (0); + GNUNET_log (GNUNET_ERROR_TYPE_INFO, + "Failed to find authorization process of client %llu for nonce `%s'\n", + client_id, + hc->path); return TALER_TEMPLATING_reply_error (hc->connection, "validation-unknown", MHD_HTTP_NOT_FOUND,