[Sparkasse] Device Recognition

[Clauscomputing]

Hi,
unfortunately my bank (Sparkasse) recently introduced device regnognition (Geräteerkennung). This means that every client has to be authenticated with a TAN at least once. Additionally some kind of cookie has to be stored for the next session.
I was able to make this work with Python FinTS and storing/loading the client object with docs.

Any chance to get this working again with go-hbci?

Thanks and best regards

[mitch000001]

Hi @Clauscomputing ,

In the dawn of #44 and #43 I was already looking into the whole process of decoupled TAN processes. I am on it and am trying to find a feasible way of introducing it. As far as I can tell we "just" need to wait for the Push TAN confirmation and have to specify the Job reference in the following request using a HKTAN segment.
I will keep you updated on the progress.

[Clauscomputing]

That would be great! Let me know if I can help.

[mitch000001]

Hi @Clauscomputing ,
I have build some new flows which should in general mimic all the things a HBCI client is expected to do. You can find the code here. On thing I still can't figure out is why I keep getting prompted about registering as a new device. I get it every time I try to access some data, although I am using the same client system ID.
Can you give it a try? Maybe you have an idea what's going on.

[mitch000001]

Me again, the latest commits in https://github.com/mitch000001/go-hbci/tree/issue-44 add a function to the client init which tries to register itself as a trusted device and waits for a conclusion of the bank. This version sends a TAN sync message, which gets an answer from the institute telling that the signature is malformed. Not sure why actually.

[Clauscomputing]

Thanks! I'll have a look!

[Clauscomputing]

Hi @mitch000001 ,

just gave it a try and it stops with

HIRMG:2:2+9050::Die Nachricht enthält Fehler.+9800::Dialog abgebrochen+9110::Falsche Segmentzusammenstellung:HKTAN:segvers=7:option=910'

910 "chipTAN manuell" would be correct...