taler-docs

Documentation for GNU Taler components, APIs and protocols
Log | Files | Refs | README | LICENSE

commit 1c356f81ea3051aa443e61e951aace709e90d25d
parent dc4f9495b8edbd27de700ed624ce7da2bc94d426
Author: MS <ms@taler.net>
Date:   Sat, 29 May 2021 09:54:02 +0200

'Bearer' was missing from manpage example

Diffstat:
Mmanpages/taler-merchant-httpd.1.rst | 2+-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/manpages/taler-merchant-httpd.1.rst b/manpages/taler-merchant-httpd.1.rst @@ -35,7 +35,7 @@ Options **-a** *TOKEN* \| **––auth=**\ \ *TOKEN* Use TOKEN for initial access control to the merchant backend. The value given in TOKEN must appear in backoffice requests to the default instance - of the merchant, i.e. "Authorization: secret-token:TOKEN" to obtain + of the merchant, i.e. "Authorization: Bearer secret-token: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