challenger

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

commit 3be28f75159fe713ee9313db5c6cba4aa80a2618
parent e035bc223cf393655f2118fb1a807956055c2bfa
Author: Christian Grothoff <grothoff@gnunet.org>
Date:   Mon, 13 Jul 2026 20:50:31 +0200

fix copy-and-paste comment

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

diff --git a/src/include/challenger-database/authorize_start.h b/src/include/challenger-database/authorize_start.h @@ -30,10 +30,11 @@ /** - * Set the user-provided address in a validation process. Updates - * the address and decrements the "addresses left" counter. If the - * address did not change, the operation is successful even without - * the counter change. + * Begin the authorization phase of a validation: record the client's OAuth2 + * scope, state, redirect URI and PKCE code challenge on the validation + * identified by @a nonce, and return the current status (last address, + * remaining attempt counters, whether it is already solved). Succeeds only if + * the supplied @a client_redirect_uri matches the one registered for the client. * * @param cls * @param nonce unique nonce to use to identify the validation