[GNC-dev] gnucash-devel Digest, Vol 215, Issue 9

[Bob White]

Scott,

After about 45 minutes on the phone with USAA being transferred to no less than 3 reps it turns out all one needs to do to reset the lock on Quicken access for USAA is visit:

www.usaa.com/accessid

And resubmit the form.

Also, once unlocked I was able to get two successful requests submitted via curl:

ACCTINFOTRNRQ:

OFXHEADER:100
DATA:OFXSGML
VERSION:103
SECURITY:NONE
ENCODING:USASCII
CHARSET:NONE
COMPRESSION:NONE
OLDFILEUID:NONE
NEWFILEUID:NONE

<OFX>
<SIGNONMSGSRQV1>
<SONRQ>
<DTCLIENT>20210210010544.000
<USERID>XXXXXXX
<USERPASS>XXXXXXX
<LANGUAGE>ENG
<FI>
<ORG>USAA Federal Savings Bank
<FID>67811
</FI>
<APPID>QMOFX
<APPVER>2300
<CLIENTUID>XXXXXXXX-17AE-42CC-9AE4-XXXXXXXXXXXX
</SONRQ>
</SIGNONMSGSRQV1>
<SIGNUPMSGSRQV1>
<ACCTINFOTRNRQ>
<TRNUID>25B63B5A-7E11-4B65-8D3C-EABB4407B7EE
<ACCTINFORQ>
<DTACCTUP>19900101
</ACCTINFORQ>
</ACCTINFOTRNRQ>
</SIGNUPMSGSRQV1>
</OFX>

And STMTTRNRQ:

OFXHEADER:100
DATA:OFXSGML
VERSION:103
SECURITY:NONE
ENCODING:USASCII
CHARSET:1252
COMPRESSION:NONE
OLDFILEUID:NONE
NEWFILEUID:12F4539B-75E1-4B37-9A82-D97C0EB4E566

<OFX>
<SIGNONMSGSRQV1>
<SONRQ>
<DTCLIENT>20210210010359.000
<USERID>XXXXXXX
<USERPASS>XXXXXXX
<LANGUAGE>ENG
<FI>
<ORG>USAA Federal Savings Bank
<FID>67811
</FI>
<APPID>QMOFX
<APPVER>2300
<CLIENTUID>XXXXXXXX-17AE-42CC-9AE4-XXXXXXXXXXXX
</SONRQ>
</SIGNONMSGSRQV1>
<BANKMSGSRQV1>
<STMTTRNRQ>
<TRNUID>A86DD084-6ADF-42EB-A410-F52CFD6333AA
<CLTCOOKIE>1
<STMTRQ>
<BANKACCTFROM>
<BANKID>314074269
<ACCTID>000XXXXXXX
<ACCTTYPE>CHECKING
</BANKACCTFROM>
<INCTRAN>
<DTSTART>20210120000000.000
<DTEND>20210208000000.000
<INCLUDE>Y
</INCTRAN>
</STMTRQ>
</STMTTRNRQ>
</BANKMSGSRQV1>
</OFX>

The results lead me to believe NEWFILEUID is not required and can be NONE.

What files need to be updated under the GnuCash.app to use the latest aqbanking lib with Martin's recent changes?

Regards,

Bob

On February 9, 2021 at 12:00 PM, gnucash-devel-request at gnucash.org wrote:


You can try unlinking Quicken from your USAA account settings page (under
Apps) and then re-activate it?

On Mon, Feb 8, 2021 at 11:47 AM Bob White <white.b at me.com> wrote:

Scott,

To expand a bit more on your research, it turns I got myself locked out
working via command line (had a typo in my password,) but I got a new
response: