[taler-docs] branch master updated (2175036 -> 402268e)

[gnunet]

This is an automated email from the git hooks/post-receive script.

ttn pushed a change to branch master
in repository docs.

    from 2175036  mention ‘sandbox ebicssubscriber list’ in the context of 
‘sandbox demobank new-ebicssubscriber’
     new e80d4e4  expand note preceding ‘libeufin-cli connections 
new-ebics-connection’
     new 402268e  mention commands to check ‘libeufin-cli connections 
new-ebics-connection’

The 2 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:
 libeufin/nexus-tutorial.rst | 10 +++++++++-
 1 file changed, 9 insertions(+), 1 deletion(-)

diff --git a/libeufin/nexus-tutorial.rst b/libeufin/nexus-tutorial.rst
index 7a2738f..f2fd52d 100644
--- a/libeufin/nexus-tutorial.rst
+++ b/libeufin/nexus-tutorial.rst
@@ -446,6 +446,11 @@ Next, we create a EBICS *bank connection* that nexus can 
use to communicate with
    ``LIBEUFIN_SANDBOX_URL`` suffixed with ``/ebicsweb``,
    since the sandbox will be providing EBICS services.
 
+   Similarly, ``EBICS_HOST_ID`` should be ``testhost``,
+   and ``EBICS_PARTNER_ID`` should be ``partner01``.
+   For ``EBICS_USER_ID`` we will use ``user02`` (for account ``jrluser``),
+   and for ``CONNECTION_NAME``, we will use ``conn01``.
+
 .. code-block:: console
 
   $ libeufin-cli \
@@ -457,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.

-- 
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.