challenger

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

commit 834d6652a93e213520e77cf57edd83954bb07a29
parent 05b24189c534bae6d270ce32d122a2d767c50ab6
Author: Christian Grothoff <grothoff@gnunet.org>
Date:   Thu, 16 Jul 2026 00:08:13 +0200

-doc fixes

Diffstat:
Msrc/include/challenger-database/authorize_start.h | 7+++++--
1 file changed, 5 insertions(+), 2 deletions(-)

diff --git a/src/include/challenger-database/authorize_start.h b/src/include/challenger-database/authorize_start.h @@ -51,8 +51,11 @@ * @param[out] solved set to true if the challenge is already solved * @param[out] last_tx_time set to the last time when we (presumably) send a PIN to @a last_address; 0 if never sent * @return transaction status: - * #GNUNET_DB_STATUS_SUCCESS_ONE_RESULT if the address was changed - * #GNUNET_DB_STATUS_SUCCESS_NO_RESULTS if we do not permit further changes to the address (attempts exhausted) + * #GNUNET_DB_STATUS_SUCCESS_ONE_RESULT if the validation exists and the + * OAuth2 scope/state/redirect/PKCE parameters were recorded + * #GNUNET_DB_STATUS_SUCCESS_NO_RESULTS if no validation matches @a nonce and + * @a client_id, or the supplied @a client_redirect_uri does not match the + * redirect URI registered for the client * #GNUNET_DB_STATUS_HARD_ERROR on failure */ enum GNUNET_DB_QueryStatus