more GLS instructions

1 files changed, 32 insertions, 12 deletions

diff --git a/doc/gls.txt b/doc/gls.txt
index 1f2f534..f474d2f 100644
--- a/doc/gls.txt
+++ b/doc/gls.txt
@@ -1,25 +1,25 @@
 ### ---- key based access.  Extracted from https://www.aquamaniac.de/sites/download/download.php?package=09&release=09&file=01&dummy=aqbanking4-handbook-20091231.pdf
 
 # 1 Create local keys _container_ (so no keys are created yet).
-gct-tool create -t ohbci output.medium
+$ gct-tool create -t ohbci output.medium
 
 # 2 Create user associated with local keys. (From now on, ${UNIQUEID} points to this fresh user)
-aqhbci-tool4 adduser -s 'https://hbci.gad.de' -u VRK588XXXX -c VRK588XXX -N 67264051XXX -b 43060967 -t ohbci --context=1 --rdhtype=0 --hbciversion=300 -n output.medium
+$ aqhbci-tool4 adduser -s 'https://hbci.gad.de' -u VRK588XXXX -c VRK588XXX -N 67264051XXX -b 43060967 -t ohbci --context=1 --rdhtype=0 --hbciversion=300 -n output.medium
 
 # 3 Get keys (sign & crypt) from the bank.  Didn't work.
-aqhbci-tool4 getkeys --user=${UNIQUEID}
+$ aqhbci-tool4 getkeys --user=${UNIQUEID}
 
 # 4 Show local (container) and bank's keys.  No warnings reported, but neither keys hashcodes. 
-gct-tool showkey -t ohbci -n output.medium
+$ gct-tool showkey -t ohbci -n output.medium
 
 # 5 Actually create keys now.  Worked.
-aqhbci-tool4 createkeys --user=${USER}
+$ aqhbci-tool4 createkeys --user=${USER}
 
 # 6 Send keys to the bank.  Didn't work (I suspect the URL associate with the user is not right).
-aqhbci-tool4 sendkeys --user=${USER}
+$ aqhbci-tool4 sendkeys --user=${USER}
 
 # 7 Last, generate letter.  Worked.
-aqhbci-tool4 iniletter --user=${USER} > ini.txt
+$ aqhbci-tool4 iniletter --user=${USER} > ini.txt
 
 # 8 Pen-sign the letter and send via snail mail to the bank.
 
@@ -27,20 +27,40 @@ aqhbci-tool4 iniletter --user=${USER} > ini.txt
 
 # Add a user in the system.  The user has a bank and a customer id,
 # but is _not_ active yet (see commands below).
-aqhbci-tool4 adduser -s 'https://hbci-pintan.gad.de/cgi-bin/hbciservlet' -u VRK588XXX -c VRK588XXX -N 6726405XXX -b 43060967 -t pintan --context=1
+$ aqhbci-tool4 adduser -s 'https://hbci-pintan.gad.de/cgi-bin/hbciservlet' -u VRK588XXX -c VRK588XXX -N 6726405XXX -b 43060967 -t pintan --context=1
 
 # Then get the "sysid".
-aqhbci-tool4 getsysid --user=U
+$ aqhbci-tool4 getsysid --user=U
 
 # Finally, give the following command to "unlock" the user.
-aqhbci-tool4 getitanmodes --user=U
+$ aqhbci-tool4 getitanmodes --user=U
 
 # If the three commands above all worked out, then balance
 # and transactions list should be available.  Try this with
 # the following commands.
 
-aqbanking-cli request --balance
+$ aqbanking-cli request --balance
 
 # and
 
-aqbanking-cli request --transactions
+$ aqbanking-cli request --transactions
+
+# At this point, we need to workaround the lack of a BIC code
+# in the configuration, in order to be able to get the PIN by
+# phone.  Say the BIC is BANKBIC, edit the following file adding
+# a 'bic=BANKBIC' line next to the other details in the upper part
+# of the file:
+
+~/.aqbanking/settings6/accounts/<unique-user-id>.conf
+
+# If the previous step worked, then issue a SEPA transfer with:
+
+$ aqbanking-cli sepatransfer --aid=<bank-account-id> --riban='DEXXX' --value="1,00:EUR" --rbic="REMOBIC" --rname="Remote Owner Name" --purpose="Test transfer 2" --name="Issuer Name" -E "Test 222"
+
+# NOTE: <bank-account-id> is the id number that Aqbanking gives
+# to bank accounts (not users!).  It can be seen by the following
+# command:
+
+$ aqbanking-cli listaccs
+
+# <bank-account-id> is now found in the second to last field.