challenger

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

commit e770e18dd229379e0289b1afa07af52f71e79e43
parent 940fb51a14a915a281011238252f45aef0d97fe8
Author: Bohdan Potuzhnyi <potub1@bfh.ch>
Date:   Sat, 10 Aug 2024 16:54:30 +0200

small changes to logs and db function names

Diffstat:
Msrc/challenger/challenger-httpd_token.c | 4++--
Msrc/challengerdb/pg_authorize_start_pkce.c | 2+-
Msrc/challengerdb/pg_validation_get_pkce.c | 2+-
3 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/src/challenger/challenger-httpd_token.c b/src/challenger/challenger-httpd_token.c @@ -387,7 +387,7 @@ CH_handler_token (struct CH_HandlerContext *hc, hc->connection, MHD_HTTP_INTERNAL_SERVER_ERROR, TALER_EC_GENERIC_DB_FETCH_FAILED, - "validation_get"); + "validation_get_pkce"); case GNUNET_DB_STATUS_SOFT_ERROR: GNUNET_break (0); return MHD_NO; @@ -398,7 +398,7 @@ CH_handler_token (struct CH_HandlerContext *hc, MHD_HTTP_UNAUTHORIZED, "invalid_grant", TALER_EC_CHALLENGER_GENERIC_VALIDATION_UNKNOWN, - "validation_get"); + "validation_get_pkce"); case GNUNET_DB_STATUS_SUCCESS_ONE_RESULT: break; } diff --git a/src/challengerdb/pg_authorize_start_pkce.c b/src/challengerdb/pg_authorize_start_pkce.c @@ -82,7 +82,7 @@ CH_PG_authorize_start_pkce (void *cls, *last_address = NULL; PREPARE (pg, - "authorize_start_validation", + "authorize_start_validation_pkce", "UPDATE validations SET" " client_scope=$3" " ,client_state=$4" diff --git a/src/challengerdb/pg_validation_get_pkce.c b/src/challengerdb/pg_validation_get_pkce.c @@ -74,7 +74,7 @@ CH_PG_validation_get_pkce (void *cls, *client_state = NULL; *address = NULL; PREPARE (pg, - "validation_get", + "validation_get_pkce", "SELECT " " client_secret" " ,address"