commit f83596b2dc44bc93c33c7b251971ba2eedbc4ff3
parent fa22f2164c39859a364aa0e852a655d550971a26
Author: Christian Grothoff <christian@grothoff.org>
Date: Sun, 30 Mar 2025 14:01:22 +0200
new options for templating messages
Diffstat:
1 file changed, 8 insertions(+), 0 deletions(-)
diff --git a/manpages/challenger.conf.5.rst b/manpages/challenger.conf.5.rst
@@ -74,6 +74,14 @@ ADDRESS_TYPE
ADDRESS_RESTRICTIONS
JSON object with a map of keys (names of the fields of the address to be entered by the user) to objects with a "regex" (string) containing an extended Posix regular expression for allowed address field values, and a "hint"/"hint_i18n" giving a human-readable explanation to display if the value entered by the user does not match the regex. Keys that are not mapped to such an object have no restriction on the value provided by the user. Examples would be '{"email":{"hint":"valid e-mail address required","regex":"^[a-zA-Z0-9\_.+-]+@[a-zA-Z0-9-]+\.[a-zA-Z0-9-.]+$"}' or '{"zip":{"hint":"numeric zip code required","regex":"^[0-9]+$"}'.
+MESSAGE_TEMPLATE_FILE
+ Name of a file with a Mustach template to use to generate the challenge message for the customer. The template will be provided the PIN/TAN under ``{{pin}}``, the customer's address in JSON format under ``{{address}}`` and the URL of the challenger backend under ``{{challenger_url}}``.
+
+BASE_URL
+ The base URL under which the challenger can be reached.
+ Provided to message templates to remind users where they
+ need to enter the challenge.
+
SEE ALSO
========
