taler-docs

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

commit caf4feb4f1dbf9d9903f41c53ff6a11781c3957e
parent 85d1f0a0def91ee0fafccdde7fdf9c514b1a486b
Author: Christian Grothoff <christian@grothoff.org>
Date:   Sat,  2 Mar 2024 19:33:15 +0100

-fix build ERROR

Diffstat:
Mfrags/nexus-ebics-setup.rst | 6+++---
1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/frags/nexus-ebics-setup.rst b/frags/nexus-ebics-setup.rst @@ -38,7 +38,7 @@ The following snippet shows the mandatory configuration values: This combination of HOST_ID, USER_ID and PARTNER_ID must never be used by another instance of libeufin-nexus or by other EBICS clients, otherwise data will be lost. Reuse existing client keys -^^^^^^^^^^^^^^^^^^^^^^^^^^ +-------------------------- If you have client keys from a previous EBICS setup you can copy the JSON file to the configured path ``CLIENT_PRIVATE_KEYS_FILE`` (``/var/lib/libeufin-nexus/client-ebics-keys.json`` with the default config). @@ -49,7 +49,7 @@ Make sure this file is accessible to the user running ``libeufin-nexus``, for th $ chown libeufin-nexus:libeufin-nexus /var/lib/libeufin-nexus/client-ebics-keys.json Create new client keys -^^^^^^^^^^^^^^^^^^^^^^ +---------------------- Assuming that the configuration file exists at ``$CONFIG_FILE``, the following command should start the EBICS setup process: @@ -69,7 +69,7 @@ file with keys created at '/tmp/libeufin-nexus-keys-$TIMESTAMP.pdf'``. Once the bank has received and processed this document you can continue. Get bank keys -^^^^^^^^^^^^^ +------------- Assuming that the configuration file exists at ``$CONFIG_FILE``, the following command will finish the EBICS setup process: