summaryrefslogtreecommitdiff
path: root/manpages/taler-merchant-httpd.1.rst
diff options
context:
space:
mode:
Diffstat (limited to 'manpages/taler-merchant-httpd.1.rst')
-rw-r--r--manpages/taler-merchant-httpd.1.rst7
1 files changed, 4 insertions, 3 deletions
diff --git a/manpages/taler-merchant-httpd.1.rst b/manpages/taler-merchant-httpd.1.rst
index 5ea47c12..3df4f4ac 100644
--- a/manpages/taler-merchant-httpd.1.rst
+++ b/manpages/taler-merchant-httpd.1.rst
@@ -13,6 +13,7 @@ Synopsis
========
**taler-merchant-httpd**
+[**-a**_|_**--auth**]
[**-C** | **--connection-close**]
[**-c** *FILENAME* | **--config=**\ \ *FILENAME*]
[**-h** | **--help**]
@@ -33,9 +34,9 @@ Options
=======
**-a** *TOKEN* \| **--auth=**\ \ *TOKEN*
- Use TOKEN for initial access control to the merchant backend. The value
+ Use TOKEN for initial access control to the merchant backend. TOKEN must start with the "secret-token:" prefix, as per RFC 8959. The value
given in TOKEN must appear in backoffice requests to the default instance
- of the merchant, i.e. "Authorization: Bearer secret-token:TOKEN" to obtain
+ of the merchant, i.e. "Authorization: Bearer TOKEN" to obtain
access to the merchant backend. Note that setting a passphrase for the
default instance by any means will block future access via TOKEN. This
is basically a way to reset the passphrase protecting access. TOKEN
@@ -92,7 +93,7 @@ TALER_MERCHANT_TOKEN
See Also
========
-taler-merchant-dbinit(1), taler-merchant-tip-enable(1), taler.conf(5)
+taler-merchant-dbinit(1), taler-merchant-setup-reserve(1), taler.conf(5)
Bugs