challenger

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

commit e5f0aa0e4b92febfbeb29f639ce616bc51119ca3
parent 5b159a3c339c81667d815c22d5fdb3cdf5c64308
Author: Christian Grothoff <christian@grothoff.org>
Date:   Sun, 26 Apr 2026 09:04:52 +0200

stick to spec, return 404

Diffstat:
Msrc/challenger/challenger-httpd_token.c | 2+-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/challenger/challenger-httpd_token.c b/src/challenger/challenger-httpd_token.c @@ -330,7 +330,7 @@ CH_handler_token (struct CH_HandlerContext *hc, GNUNET_break_op (0); return CH_reply_with_oauth_error ( hc->connection, - MHD_HTTP_UNAUTHORIZED, + MHD_HTTP_NOT_FOUND, "invalid_client", TALER_EC_CHALLENGER_GENERIC_CLIENT_UNKNOWN, NULL);