taler-docs

commit 9a7f61b386e8bfa394716c27ebbe049caab48a88
parent 285a6b15ee5f01c5dce1e1c4a816528313ad5567
Author: Christian Grothoff <grothoff@gnunet.org>
Date:   Tue, 14 Jul 2026 22:56:56 +0200

document how to provision the client secret via environment variable

Diffstat:
M
manpages/challenger-admin.1.rst
 | 
6
++++++

1 file changed, 6 insertions(+), 0 deletions(-)
diff --git a/manpages/challenger-admin.1.rst b/manpages/challenger-admin.1.rst
@@ -35,6 +35,12 @@ Its options are as follows:
 **-a** *CLIENT_SECRET* \| **--add=**\ ‌\ *CLIENT_SECRET*
    Add the client with the given *CLIENT_REDIRECT_URL setting the client secret to *CLIENT_SECRET*.  Prints the *CLIENT_ID* of the added client. The *CLIENT_SECRET* must begin with "secret-token:" as per RFC 8959.
 
+   Passing the client secret via the command-line exposes it to other
+   users on the same host. If that is a concern, it is also possible
+   to set the client secret via the
+   ``CHALLENGER_CLIENT_SECRET`` environment variable. If both are
+   set, the command-line version is preferred. 
+
 **-c** *FILENAME* \| **--config=**\ ‌\ *FILENAME*
    Use the configuration and other resources for the Challenger commands
    to operate from *FILENAME*.