commit f56753c083eab08a3c4aa9a0b82d3ade0d253375
parent 0aadbd53ba08f672280aac1c040776e4982c8f64
Author: Christian Grothoff <christian@grothoff.org>
Date: Mon, 15 Apr 2024 01:08:24 +0200
-fix notes
Diffstat:
1 file changed, 16 insertions(+), 16 deletions(-)
diff --git a/taler-challenger-manual.rst b/taler-challenger-manual.rst
@@ -225,9 +225,9 @@ Fundamental Setup: Address validation
Each challenger service is designed to validate one type of address. Possible
address types include:
- * phone numbers (via SMS)
- * e-mail addresses (via SMTP)
- * mail addresses (via postal service)
+* phone numbers (via SMS)
+* e-mail addresses (via SMTP)
+* mail addresses (via postal service)
In principle, additional types of addresses can easily be added by extending
the respective HTML and programs to send challenges to the new address type.
@@ -235,17 +235,17 @@ the respective HTML and programs to send challenges to the new address type.
To make different types of address validations possible, the Challenger
configuration contains two configuration options.
- (1) The ``ADDRESS_TYPE`` configuration option informs Challenger about the
- type of address it is expected to validate. It is returned as part of
- the OAuth 2.0 ``/info`` endpoint to the client, and is typically also
- used when deciding how to render the HTML form for address entry that is
- shown to the user.
+(1) The ``ADDRESS_TYPE`` configuration option informs Challenger about the
+ type of address it is expected to validate. It is returned as part of
+ the OAuth 2.0 ``/info`` endpoint to the client, and is typically also
+ used when deciding how to render the HTML form for address entry that is
+ shown to the user.
- (2) The ``AUTH_COMMAND`` configuration option specifies which command
- Challenger should run to send a challenge to an address. The actual
- address is given to this subcommand as the first argument (``$1``),
- while the text with the challenge is passed to standard input.
- The subcommand should terminate with a status code of 0 on success.
+(2) The ``AUTH_COMMAND`` configuration option specifies which command
+ Challenger should run to send a challenge to an address. The actual
+ address is given to this subcommand as the first argument (``$1``),
+ while the text with the challenge is passed to standard input.
+ The subcommand should terminate with a status code of 0 on success.
.. code-block:: ini
:caption: /etc/challenger/challenger.conf
@@ -264,10 +264,10 @@ the SMS and postal mail scripts before they can function. In any case, these
scripts should be primarily seen as *examples* on how to write authentication
commands.
- ..note::
+.. note::
- We strongly welcome contributions for additional scripts with alternative
- providers or for new types of addresses.
+ We strongly welcome contributions for additional scripts with alternative
+ providers or for new types of addresses.
Legal conditions for using the service
