taler-docs

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

commit 92288b2ecfcc77a4123c9bdcec61750cd2da2947
parent 4eb57258638444891348b1390e22e521a0c46de9
Author: Antoine A <>
Date:   Tue, 29 Oct 2024 18:39:28 +0100

corebank: deprecate password auth

Diffstat:
Mcore/api-corebank.rst | 20++++++++------------
1 file changed, 8 insertions(+), 12 deletions(-)

diff --git a/core/api-corebank.rst b/core/api-corebank.rst @@ -35,18 +35,14 @@ it provides features for local/regional currencies. Authentication -------------- -Some requests require the client to authenticate via HTTP Basic auth (RFC 7617) -or using a bearer token which can be obtained or refreshed from the -``/accounts/$USERNAME/token`` endpoint. -When using Basic authentication, the user-id must be the bank -username, and the password the password for the corresponding user. - -Another way to obtain a login token is by manually configuring it for certain -endpoints. For example, the exchange could give an auditor read-only access to -the taler-wire-gateway facade via such a manually configured access token. - -The ``admin`` user is a special, hard-coded username. Some requests require the -client to authenticate as the admin. +Some endpoints requires the client to authenticate using a bearer token. Tokens can be obtained or refreshed using the ``/accounts/$USERNAME/token`` endpoint. +This endpoint support authentication via HTTP Basic auth (RFC 7617). When using Basic authentication, the user-id must be the bank's username, and the password the password of the corresponding user. + +The user ``admin`` is a special, hard-coded username. Some requests require the client to authenticate as administrator. + +.. warning:: + + Basic authentication for endpoints other than ``/accounts/$USERNAME/token`` has been deprecated and will no longer be supported in the next release. .. http:post:: /accounts/$USERNAME/token