taler-docs

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

commit 402268ec81c17999c02fe016ffca0a3480e8c5fb
parent e80d4e40fdfb9d610b475c9cc234b6a3be8254f7
Author: Thien-Thi Nguyen <ttn@gnuvola.org>
Date:   Thu, 24 Feb 2022 06:22:51 -0500

mention commands to check ‘libeufin-cli connections new-ebics-connection’

Diffstat:
Mlibeufin/nexus-tutorial.rst | 5++++-
1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/libeufin/nexus-tutorial.rst b/libeufin/nexus-tutorial.rst @@ -462,7 +462,10 @@ Next, we create a EBICS *bank connection* that nexus can use to communicate with --ebics-user-id $EBICS_USER_ID \ $CONNECTION_NAME -If this step executes correctly, Nexus will have created all the cryptographic +If this step executes correctly +(use ``libeufin-cli connections list-connections`` +and ``libeufin-cli connections show-connection`` to check), +Nexus will have created all the cryptographic material that is needed on the client side; in this EBICS example, it created the signature and identification keys. It is therefore advisable to *make a backup copy* of such keys.