[taler-docs] branch master updated: EBICS 3 tutorial: confirming keys

[gnunet]

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

ms pushed a commit to branch master
in repository docs.

The following commit(s) were added to refs/heads/master by this push:
     new 416bc151 EBICS 3 tutorial: confirming keys
416bc151 is described below

commit 416bc151ac9fa4d5a2eab26231cdac3c5d2ef39a
Author: MS <ms@taler.net>
AuthorDate: Tue Jul 11 11:29:46 2023 +0200

    EBICS 3 tutorial: confirming keys
---
 libeufin/ebics3-test-tutorial.rst |  23 ++++++++++++++++++++---
 libeufin/set-EBICS-keys.png       | Bin 0 -> 143389 bytes
 2 files changed, 20 insertions(+), 3 deletions(-)

diff --git a/libeufin/ebics3-test-tutorial.rst 
b/libeufin/ebics3-test-tutorial.rst
index 52967b57..5aac8868 100644
--- a/libeufin/ebics3-test-tutorial.rst
+++ b/libeufin/ebics3-test-tutorial.rst
@@ -86,13 +86,13 @@ Clone the following repository:
 
    git://git.taler.net/deployment
 
-Navigate in the following directory
+navigate in the following directory
 
 .. code-block:: shell-session
 
    deployment/nlnet/task3
 
-And build the Docker image with the following command:
+and build the Docker image with the following command:
 
 .. code-block:: shell-session
 
@@ -103,7 +103,7 @@ If the previous steps succeeded, the *pofi* image is ready 
to be run.
 .. note::
   
    Although the test runner guides the user via live instructions,
-   it's advised to read the `Testing description`_ section.
+   it's advised to read the `Test details`_ section.
 
 The test runner needs the following two values: EBICS user ID and EBICS
 partner ID.  The `previous section <get-ebics-ids_>`_ explains how
@@ -113,6 +113,23 @@ to get them.
 
   docker run -it pofi $EBICS_USER_ID $EBICS_PARTNER_ID
 
+Right after the start, the test runner needs the user intervention to
+confirm the user keys at the bank side.  For this reason, it will pause
+the execution until the user is done.  The following screenshot shows
+how to navigate to the page where the user has to intervene:
+
+.. image:: get-EBICS-IDs-0.png
+
+Once obtaining the page below, box #1 resets potential previous uploaded
+keys (only required when running the test more than once), and box #2 confirms
+the newly uploaded keys.  Note: in production cases, such confirmation happens
+via the traditional paper mail.
+
+.. image:: set-EBICS-keys.png
+
+After having confirmed the new keys, the execution can be resumed to
+let the test runner proceed with the uploading and downloading operations.
+
 Test details
 ------------
 
diff --git a/libeufin/set-EBICS-keys.png b/libeufin/set-EBICS-keys.png
new file mode 100644
index 00000000..71ecfa86
Binary files /dev/null and b/libeufin/set-EBICS-keys.png differ

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