summaryrefslogtreecommitdiff
path: root/taler-exchange-setup-guide.rst
diff options
context:
space:
mode:
authorMS <ms@taler.net>2021-08-06 07:40:47 -1100
committerMS <ms@taler.net>2021-08-06 07:41:30 -1100
commit1986a8171f2281b870198596d214be232c7b1b65 (patch)
treece9988088267f72a44b14a624dee14757790aef2 /taler-exchange-setup-guide.rst
parent5370cdc8f37087dc82d4a71d4228563bcb90b95a (diff)
downloaddocs-1986a8171f2281b870198596d214be232c7b1b65.tar.gz
docs-1986a8171f2281b870198596d214be232c7b1b65.tar.bz2
docs-1986a8171f2281b870198596d214be232c7b1b65.zip
-fixes + fixme notes (exchange setup guide)
Diffstat (limited to 'taler-exchange-setup-guide.rst')
-rw-r--r--taler-exchange-setup-guide.rst23
1 files changed, 18 insertions, 5 deletions
diff --git a/taler-exchange-setup-guide.rst b/taler-exchange-setup-guide.rst
index af939784..590f4bae 100644
--- a/taler-exchange-setup-guide.rst
+++ b/taler-exchange-setup-guide.rst
@@ -348,9 +348,9 @@ Connecting Nexus with an EBICS account
The command line interface of the LibEuFin nexus needs the following three
values to be defined in the environment: ``LIBEUFIN_NEXUS_URL``,
``LIBEUFIN_NEXUS_USERNAME``, and ``LIBEUFIN_NEXUS_PASSWORD``. In this example,
-``LIBEUFIN_NEXUS_USERNAME`` should be set to ``foo``, and
-``LIBEUFIN_NEXUS_PASSWORD`` to the value given for its password in the previous
-step (with the ``libeufin-nexus superuser`` command). The
+``LIBEUFIN_NEXUS_USERNAME`` should be set to ``admin``, and
+``LIBEUFIN_NEXUS_PASSWORD`` to the value hold in ``NEXUS_ADMIN_PW`` from the
+previous step (the ``libeufin-nexus superuser`` command). The
``LIBEUFIN_NEXUS_URL`` could be given as ``http://localhost:5017/``.
Next, we create a EBICS *bank connection* that nexus can use to communicate with the bank.
@@ -499,7 +499,7 @@ The following command prepares a payment:
$LOCAL_ACCOUNT_NAME
Note: the ``$AMOUNT`` value needs the format ``X.Y:CURRENCY``; for example
-``10:EUR``, or ``1.01:EUR``.
+``EUR:10``, or ``EUR:1.01``.
The previous command should return a value (``$UUID``) that uniquely
identifies the prepared payment in the Nexus system. That is needed
@@ -570,6 +570,14 @@ INI and HIA secret keys will be restored for the requesting user.
--backup-file=$BACKUP_FILE \
$CONNECTION_NAME
+..
+ FIXME: this section, although useful, doesn't really belong
+ to the flow here. It is very unlikely that the reader needs
+ to restore the backup just here. Maybe move next to the create-backup
+ command as a note, or simply remove it entirely from this guide.
+
+ Also worth noting: on a bad password given, Nexus responds
+ "bad backup given" instead of "authentication failed".
Creating a Taler facade
~~~~~~~~~~~~~~~~~~~~~~~
@@ -597,7 +605,7 @@ here to API here) API becomes offered by the Nexus. The purpose
is to let a Taler exchange rely on Nexus to manage its bank account.
The base URL of the facade that can be used by the Taler exchange
-as the Taler Wire Gateway base URL located when listing the facades:
+as the Taler Wire Gateway base URL can be seen by listing the facades:
.. code-block:: console
@@ -640,6 +648,11 @@ and create payment initiations with a Taler wire gateway facade:
facade $FACADENAME \
facade.talerWireGateway.transfer
+..
+ FIXME: the two commands above output a empty JSON object
+ when successful. Possibly, we should suppress that (just like
+ the other commands do)
+
The list of all granted permissions can be reviewed:
.. code-block:: console