commit 735765c0f57de3f8121dfdf715635c667f818375
parent 7a6017b7f9221ce45636fd232405182e2b76b9bd
Author: Martin Schanzenbach <schanzen@gnunet.org>
Date: Sun, 6 Jul 2025 16:57:51 +0200
no ext auth in v20
Diffstat:
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/core/api-merchant.rst b/core/api-merchant.rst
@@ -97,7 +97,7 @@ of that instance.
Currently, the ``/private/auth/`` API supports two main authentication methods in the ``InstanceAuthConfigurationMessage``:
-* ``external``: (*@deprecated since vNOEXTAUTH*) With this method, no checks are done by the merchant backend.
+* ``external``: (*@deprecated since v20*) With this method, no checks are done by the merchant backend.
Instead, a reverse proxy / API gateway must do all authentication/authorization checks.
* ``token`` (**@since v19**): With this method, the client must provide an authorization header
that contains a bearer token when accessing a protected endpoint in the form
@@ -1202,7 +1202,7 @@ Setting up instances
.. ts:def:: InstanceAuthConfigExternal
- // @deprecated vNOEXTAUTH
+ // @deprecated v20
interface InstanceAuthConfigExternal {
// The mechant backend does not do
// any authentication checks. Instead an API
