taler-docs

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

commit 89c858d56a492e3a6f370b74c5d16c8b610e8702
parent aacf89d4c3b641eb6a4f5ca261445dd43ab1c4ee
Author: MS <ms@taler.net>
Date:   Tue, 10 Oct 2023 12:45:21 +0200

DD50: EBICS client keyS (plural)

Diffstat:
Mdesign-documents/050-libeufin-nexus.rst | 10++--------
1 file changed, 2 insertions(+), 8 deletions(-)

diff --git a/design-documents/050-libeufin-nexus.rst b/design-documents/050-libeufin-nexus.rst @@ -62,7 +62,7 @@ Configuration file SYSTEM_ID = banksys ACCOUNT_NUMBER = DE1234567890 # This value must identify with how the bank calls the bank account BANK_PUBLIC_KEYS_FILE = enc-auth-keys.json - CLIENT_PRIVATE_KEY_FILE = my-private-key.json + CLIENT_PRIVATE_KEYS_FILE = my-private-keys.json ACCOUNT_META_DATA_FILE = ebics-meta.json BANK_DIALECT = postfinance # EBICS+ISO20022 style used by the bank. @@ -101,7 +101,7 @@ JSON with 3 fields: * bank_authentication_public_key (base32) * accepted (boolean) -File contents: CLIENT_PRIVATE_KEY_FILE +File contents: CLIENT_PRIVATE_KEYS_FILE ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ JSON with: @@ -171,12 +171,6 @@ The ebics-setup tool performs the following: --check-full-config, also sanity-check the configuration options of the other subsystems. -.. - Not extremely important, but: try to imitate the 'dry run' option offered - by the exchange, to avoid having a big config-check upfront, and instead - spread the check along the execution. - - * Checks if the private keys file exists, if not creates new private keys with flags "not submitted".