commit 7a6017b7f9221ce45636fd232405182e2b76b9bd
parent fdf4cb517458c0e0bdd3c6752730d77984df2bb8
Author: Martin Schanzenbach <schanzen@gnunet.org>
Date: Sun, 6 Jul 2025 16:40:52 +0200
remove duplicated deprecated info
Diffstat:
1 file changed, 0 insertions(+), 2 deletions(-)
diff --git a/core/api-merchant.rst b/core/api-merchant.rst
@@ -107,8 +107,6 @@ Currently, the ``/private/auth/`` API supports two main authentication methods i
A login token is commonly only valid for a limited period of time and scoped to specific permissions.
If the ``$INSTANCE_PASSWORD`` is lost, the administrator can set a password
using the ``taler-merchant-passwd`` command-line tool.
- Any API may also be accessed using the bearer authentication ``secret-token: $INSTANCE_PASSWORD``.
- Notice that this behaviour is deprecated and will be phased out in favor of login tokens.
* ``token`` (*@deprecated since v19*): With this method, the client must provide an authentication token in
the format ``secret-token: $INSTANCE_PASSWORD``.
The behaviour is then equivalent to the ``token`` method above.
