Thanks for the clarification. I updated aqbanking to 6.2.6 and I can see
the HTTP User Agent field now.
On Tue, Feb 16, 2021 at 11:25 AM John Ralls wrote:
> Sorry, it's AQBanking 6.2.6. I've fixed the wiki page and added links for
> macOS and flathub users to the exact version of GnuCash they
___
Date: Sun, 14 Feb 2021 11:12:26 -0800
From: John Ralls
To: Randy Johnson
Cc: gnucash-de...@gnucash.org, gnucash-user@gnucash.org
Subject: Re: [GNC] [GNC-dev] USAA FSB requires newer QWIN support
Message-ID:
Content-Type: text/plain; charset=us-ascii
Well, there's a UUID in th
The instructions on the wiki say that GnuCash 4.4 and aqbanking 6.1.6 are
required to connect, but some of the comments on this thread refer to
GnuCash 4.4.1. I tried with GnuCash 4.4 and aqbanking 6.2.5 and found that
the aqbanking UI is slightly different than described in the wiki and there
is
I ended up with two during my experimentation - I ended up requesting
access twice, I got the same access is and password both times but
different client uuids. Both client uuids I got as well as the published
one worked for me.
Quick check, did you capitalize the letters in the uuid? Someone
The CLIENTUID is also part of the URL that you get sent to after completing
https://df3cx-services.1fsapi.com/casm/usaa/enroll (or usaa.com/accessid ,
not sure which is preferred), hopefully avoiding the need to install
Quicken.
-Randy
On Fri, Feb 12, 2021, 5:29 PM Bob White via gnucash-devel <
t believe its working again. Thanks everyone.
>
> Keith
>
> _
>
> Date: Sun, 14 Feb 2021 11:12:26 -0800
> From: John Ralls
> To: Randy Johnson
> Cc: gnucash-de...@gnucash.org, gnucash-user@gnucash.org
> Subject: Re: [GNC] [GNC-dev] USAA FSB require
sh.org, gnucash-user@gnucash.org
Subject: Re: [GNC] [GNC-dev] USAA FSB requires newer QWIN support
Message-ID:
Content-Type: text/plain; charset=us-ascii
Well, there's a UUID in that URL, but I just tried using it for the
ClientUUID and got "The user cannot signon because he or she e
I tried again with a second visit to accessid so I'd get a fresh UUID. It
worked to get the accounts but failed when I tried to retrieve transactions.
I've summarized the setup process in
https://wiki.gnucash.org/wiki/OFX_Direct_Connect_Bank_Settings#USAA, though for
my experience the Client
I tried it both ways, capitalized and not.
Regards,
John Ralls
> On Feb 14, 2021, at 11:31 AM, Randy Johnson wrote:
>
> I ended up with two during my experimentation - I ended up requesting access
> twice, I got the same access is and password both times but different client
> uuids. Both
Well, there's a UUID in that URL, but I just tried using it for the ClientUUID
and got "The user cannot signon because he or she entered an invalid user ID or
password." Using the one scraped from Quicken for MacOS and reported in
10 matches
Mail list logo
