Re: [GNC-dev] [GNC] USAA FSB requires newer QWIN support
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 need.
There's no 4.4.1: We changed to a two-digit versioning system 4 years ago.
However the all-in-one bundles on macOS and Windows can have suffixes as do
flathub packages. I didn't do a rebundle of the 4.4 release on Windows as we
have nightly builds for that and users are accustomed to using them. The
flathub version you need is 4.4-4 and the macOS one is 4.4-2. For the latter
use the new link on the wiki page; I don't intend to change the link on the
website nor to add the 4.4-2 dmg to the Github release because this affects
only a few users.
Regards,
John Ralls
> On Feb 16, 2021, at 6:07 AM, John Haiducek wrote:
>
> 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 no
> field to set the HTTP User Agent. Is GnuCash 4.4.1 and/or aqbanking 6.2.6
> required to make this work?
>
> John
>
> On Sun, Feb 14, 2021 at 7:54 PM John Ralls wrote:
> 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 UID instructions, which reflect getting them
> from the URL, are not correct.
>
> Regards,
> John Ralls
>
>
> > On Feb 14, 2021, at 3:59 PM, John Ralls wrote:
> >
> > 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 client uuids I got as well as the published
> >> one worked for me.
> >> Quick check, did you capitalize the letters in the uuid? Someone mentioned
> >> it earlier and I just confirmed with my own, lower case uuids will return
> >> an error.
> >> -Randy
> >>
> >> On Sun, Feb 14, 2021, 2:12 PM John Ralls wrote:
> >> 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
> >> https://lists.gnucash.org/pipermail/gnucash-devel/2021-February/045690.html
> >> works.
> >>
> >> That leads me to believe that USAA is using the ClientUUID as an API key.
> >> Quicken may have registered one or many. I think the only way to find that
> >> out is for more users to set up MITMs with different versions of Quicken
> >> and retrieve the ClientUUIDs for comparison.
> >>
> >> This makes me a bit leery of publishing it on the wiki, because if Quicken
> >> or USAA catch on that it's been compromised they might change it and lock
> >> us out again.
> >>
> >> Regards,
> >> John Ralls
> >>
> >>
> >>> On Feb 13, 2021, at 9:06 PM, Randy Johnson wrote:
> >>>
> >>> 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 <
> >>> gnucash-devel@gnucash.org> wrote:
> >>>
> I got new USAA OFX download working with GNC 4.4.1.
>
> It's mainly a configuration task.
>
> -- User config --
> int uniqueId=""
> char backendName="aqofxconnect"
> char userName=""
> char userId=""
> char customerId=""
> char country="us"
> char bankCode="314074269"
> int lastSessionId="0"
>
> data {
> backend {
> char bankName="USAA Federal Savings Bank"
> char org="USAA Federal Savings Bank"
> char fid="67811"
> char serverAddr="https%3A%2F%2Fdf3cx-services.1fsapi.com
> %2Fcasm%2Fusaa%2Faccess.ofx"
> char appId="QMOFX"
> char appVer="2300"
> char headerVer="103"
> char clientUid=""
> int httpVMajor="0"
> int httpVMinor="0"
> char httpUserAgent="InetClntApp%2F3.0"
> } #backend
> } #data
> -
>
> Notes:
> -- 'httpUserAgent' is currently not configurable through GNC v4.4.1, but
> it works when included in the file. It has been added in newer
> AqBanking,
> look for support in next GNC release.
> -- 'CLIENTUID' can be found in OFXLog.txt generated by Quicken. Signup
> for trial and cancel
Re: [GNC-dev] [GNC] USAA FSB requires newer QWIN support
My USAA checking and credit card seem to be working. My users/0.conf is using this client UID: I got it from quicken's OFXlog.txt file. char clientUid="39E0E763-4E1E-4918-9528-D6EBAC94EF5D" Notably when the online action in GNC challenges for the account password the required response is now the "Access PIN". No longer the web site account password. Yet another password to track. I cannot believe its working again. Thanks everyone. Keith _ Date: Sun, 14 Feb 2021 11:12:26 -0800 From: John Ralls To: Randy Johnson Cc: gnucash-devel@gnucash.org, gnucash-u...@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 entered an invalid user ID or password." Using the one scraped from Quicken for MacOS and reported in https://lists.gnucash.org/pipermail/gnucash-devel/2021-February/045690.html works. That leads me to believe that USAA is using the ClientUUID as an API key. Quicken may have registered one or many. I think the only way to find that out is for more users to set up MITMs with different versions of Quicken and retrieve the ClientUUIDs for comparison. This makes me a bit leery of publishing it on the wiki, because if Quicken or USAA catch on that it's been compromised they might change it and lock us out again. Regards, John Ralls ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: [GNC-dev] [GNC] USAA FSB requires newer QWIN support
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 UID instructions, which reflect getting them from the
URL, are not correct.
Regards,
John Ralls
> On Feb 14, 2021, at 3:59 PM, John Ralls wrote:
>
> 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 client uuids I got as well as the published one worked for me.
>> Quick check, did you capitalize the letters in the uuid? Someone mentioned
>> it earlier and I just confirmed with my own, lower case uuids will return an
>> error.
>> -Randy
>>
>> On Sun, Feb 14, 2021, 2:12 PM John Ralls wrote:
>> 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
>> https://lists.gnucash.org/pipermail/gnucash-devel/2021-February/045690.html
>> works.
>>
>> That leads me to believe that USAA is using the ClientUUID as an API key.
>> Quicken may have registered one or many. I think the only way to find that
>> out is for more users to set up MITMs with different versions of Quicken and
>> retrieve the ClientUUIDs for comparison.
>>
>> This makes me a bit leery of publishing it on the wiki, because if Quicken
>> or USAA catch on that it's been compromised they might change it and lock us
>> out again.
>>
>> Regards,
>> John Ralls
>>
>>
>>> On Feb 13, 2021, at 9:06 PM, Randy Johnson wrote:
>>>
>>> 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 <
>>> gnucash-devel@gnucash.org> wrote:
>>>
I got new USAA OFX download working with GNC 4.4.1.
It's mainly a configuration task.
-- User config --
int uniqueId=""
char backendName="aqofxconnect"
char userName=""
char userId=""
char customerId=""
char country="us"
char bankCode="314074269"
int lastSessionId="0"
data {
backend {
char bankName="USAA Federal Savings Bank"
char org="USAA Federal Savings Bank"
char fid="67811"
char serverAddr="https%3A%2F%2Fdf3cx-services.1fsapi.com
%2Fcasm%2Fusaa%2Faccess.ofx"
char appId="QMOFX"
char appVer="2300"
char headerVer="103"
char clientUid=""
int httpVMajor="0"
int httpVMinor="0"
char httpUserAgent="InetClntApp%2F3.0"
} #backend
} #data
-
Notes:
-- 'httpUserAgent' is currently not configurable through GNC v4.4.1, but
it works when included in the file. It has been added in newer AqBanking,
look for support in next GNC release.
-- 'CLIENTUID' can be found in OFXLog.txt generated by Quicken. Signup
for trial and cancel within 30 days no charge.
-- 'your new USAA access id' can be found at
https://www.usaa.com/accessid
You will need to disconnect accounts from within the AqBanking Wizard,
download accounts with new user configuration, then reconnect accounts. In
my case, the new credit card account numbers in the accounts list are not a
100% match to the number found on your credit card. There were enough
common digits to know which was which, just be aware. I was able to
successfully download and update 2 checking accounts, a savings account,
and a credit card account.
I hope this helps.
Regards,
Bob
PS. I did clone the AqBanking repo and build and install the latest
libraries on the same machine I am running GNC. I am not sure if the
GNC used the libraries distributed with it or the ones I built so YMMV.
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel
>>> ___
>>> gnucash-devel mailing list
>>> gnucash-devel@gnucash.org
>>> https://lists.gnucash.org/mailman/listinfo/gnucash-devel
>>
>
> ___
> gnucash-user mailing list
> gnucash-u...@gnucash.org
> To update your subscription preferences or to unsubscribe:
>
Re: [GNC-dev] [GNC] USAA FSB requires newer QWIN support
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 client uuids I got as well as the published one worked for me.
> Quick check, did you capitalize the letters in the uuid? Someone mentioned it
> earlier and I just confirmed with my own, lower case uuids will return an
> error.
> -Randy
>
> On Sun, Feb 14, 2021, 2:12 PM John Ralls wrote:
> 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
> https://lists.gnucash.org/pipermail/gnucash-devel/2021-February/045690.html
> works.
>
> That leads me to believe that USAA is using the ClientUUID as an API key.
> Quicken may have registered one or many. I think the only way to find that
> out is for more users to set up MITMs with different versions of Quicken and
> retrieve the ClientUUIDs for comparison.
>
> This makes me a bit leery of publishing it on the wiki, because if Quicken or
> USAA catch on that it's been compromised they might change it and lock us out
> again.
>
> Regards,
> John Ralls
>
>
> > On Feb 13, 2021, at 9:06 PM, Randy Johnson wrote:
> >
> > 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 <
> > gnucash-devel@gnucash.org> wrote:
> >
> >> I got new USAA OFX download working with GNC 4.4.1.
> >>
> >> It's mainly a configuration task.
> >>
> >> -- User config --
> >> int uniqueId=""
> >> char backendName="aqofxconnect"
> >> char userName=""
> >> char userId=""
> >> char customerId=""
> >> char country="us"
> >> char bankCode="314074269"
> >> int lastSessionId="0"
> >>
> >> data {
> >> backend {
> >>char bankName="USAA Federal Savings Bank"
> >>char org="USAA Federal Savings Bank"
> >>char fid="67811"
> >>char serverAddr="https%3A%2F%2Fdf3cx-services.1fsapi.com
> >> %2Fcasm%2Fusaa%2Faccess.ofx"
> >>char appId="QMOFX"
> >>char appVer="2300"
> >>char headerVer="103"
> >>char clientUid=""
> >>int httpVMajor="0"
> >>int httpVMinor="0"
> >>char httpUserAgent="InetClntApp%2F3.0"
> >> } #backend
> >> } #data
> >> -
> >>
> >> Notes:
> >> -- 'httpUserAgent' is currently not configurable through GNC v4.4.1, but
> >> it works when included in the file. It has been added in newer AqBanking,
> >> look for support in next GNC release.
> >> -- 'CLIENTUID' can be found in OFXLog.txt generated by Quicken. Signup
> >> for trial and cancel within 30 days no charge.
> >> -- 'your new USAA access id' can be found at
> >> https://www.usaa.com/accessid
> >>
> >> You will need to disconnect accounts from within the AqBanking Wizard,
> >> download accounts with new user configuration, then reconnect accounts. In
> >> my case, the new credit card account numbers in the accounts list are not a
> >> 100% match to the number found on your credit card. There were enough
> >> common digits to know which was which, just be aware. I was able to
> >> successfully download and update 2 checking accounts, a savings account,
> >> and a credit card account.
> >>
> >> I hope this helps.
> >>
> >> Regards,
> >>
> >> Bob
> >>
> >> PS. I did clone the AqBanking repo and build and install the latest
> >> libraries on the same machine I am running GNC. I am not sure if the
> >> GNC used the libraries distributed with it or the ones I built so YMMV.
> >> ___
> >> gnucash-devel mailing list
> >> gnucash-devel@gnucash.org
> >> https://lists.gnucash.org/mailman/listinfo/gnucash-devel
> >>
> > ___
> > gnucash-devel mailing list
> > gnucash-devel@gnucash.org
> > https://lists.gnucash.org/mailman/listinfo/gnucash-devel
>
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: [GNC-dev] [GNC] USAA FSB requires newer QWIN support
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 mentioned
it earlier and I just confirmed with my own, lower case uuids will return
an error.
-Randy
On Sun, Feb 14, 2021, 2:12 PM John Ralls wrote:
> 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
> https://lists.gnucash.org/pipermail/gnucash-devel/2021-February/045690.html
> works.
>
> That leads me to believe that USAA is using the ClientUUID as an API key.
> Quicken may have registered one or many. I think the only way to find that
> out is for more users to set up MITMs with different versions of Quicken
> and retrieve the ClientUUIDs for comparison.
>
> This makes me a bit leery of publishing it on the wiki, because if Quicken
> or USAA catch on that it's been compromised they might change it and lock
> us out again.
>
> Regards,
> John Ralls
>
>
> > On Feb 13, 2021, at 9:06 PM, Randy Johnson wrote:
> >
> > 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 <
> > gnucash-devel@gnucash.org> wrote:
> >
> >> I got new USAA OFX download working with GNC 4.4.1.
> >>
> >> It's mainly a configuration task.
> >>
> >> -- User config --
> >> int uniqueId=""
> >> char backendName="aqofxconnect"
> >> char userName=""
> >> char userId=""
> >> char customerId=""
> >> char country="us"
> >> char bankCode="314074269"
> >> int lastSessionId="0"
> >>
> >> data {
> >> backend {
> >>char bankName="USAA Federal Savings Bank"
> >>char org="USAA Federal Savings Bank"
> >>char fid="67811"
> >>char serverAddr="https%3A%2F%2Fdf3cx-services.1fsapi.com
> >> %2Fcasm%2Fusaa%2Faccess.ofx"
> >>char appId="QMOFX"
> >>char appVer="2300"
> >>char headerVer="103"
> >>char clientUid=""
> >>int httpVMajor="0"
> >>int httpVMinor="0"
> >>char httpUserAgent="InetClntApp%2F3.0"
> >> } #backend
> >> } #data
> >> -
> >>
> >> Notes:
> >> -- 'httpUserAgent' is currently not configurable through GNC v4.4.1,
> but
> >> it works when included in the file. It has been added in newer
> AqBanking,
> >> look for support in next GNC release.
> >> -- 'CLIENTUID' can be found in OFXLog.txt generated by Quicken. Signup
> >> for trial and cancel within 30 days no charge.
> >> -- 'your new USAA access id' can be found at
> >> https://www.usaa.com/accessid
> >>
> >> You will need to disconnect accounts from within the AqBanking Wizard,
> >> download accounts with new user configuration, then reconnect
> accounts. In
> >> my case, the new credit card account numbers in the accounts list are
> not a
> >> 100% match to the number found on your credit card. There were enough
> >> common digits to know which was which, just be aware. I was able to
> >> successfully download and update 2 checking accounts, a savings account,
> >> and a credit card account.
> >>
> >> I hope this helps.
> >>
> >> Regards,
> >>
> >> Bob
> >>
> >> PS. I did clone the AqBanking repo and build and install the latest
> >> libraries on the same machine I am running GNC. I am not sure if the
> >> GNC used the libraries distributed with it or the ones I built so YMMV.
> >> ___
> >> gnucash-devel mailing list
> >> gnucash-devel@gnucash.org
> >> https://lists.gnucash.org/mailman/listinfo/gnucash-devel
> >>
> > ___
> > gnucash-devel mailing list
> > gnucash-devel@gnucash.org
> > https://lists.gnucash.org/mailman/listinfo/gnucash-devel
>
>
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: [GNC-dev] [GNC] USAA FSB requires newer QWIN support
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
https://lists.gnucash.org/pipermail/gnucash-devel/2021-February/045690.html
works.
That leads me to believe that USAA is using the ClientUUID as an API key.
Quicken may have registered one or many. I think the only way to find that out
is for more users to set up MITMs with different versions of Quicken and
retrieve the ClientUUIDs for comparison.
This makes me a bit leery of publishing it on the wiki, because if Quicken or
USAA catch on that it's been compromised they might change it and lock us out
again.
Regards,
John Ralls
> On Feb 13, 2021, at 9:06 PM, Randy Johnson wrote:
>
> 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 <
> gnucash-devel@gnucash.org> wrote:
>
>> I got new USAA OFX download working with GNC 4.4.1.
>>
>> It's mainly a configuration task.
>>
>> -- User config --
>> int uniqueId=""
>> char backendName="aqofxconnect"
>> char userName=""
>> char userId=""
>> char customerId=""
>> char country="us"
>> char bankCode="314074269"
>> int lastSessionId="0"
>>
>> data {
>> backend {
>>char bankName="USAA Federal Savings Bank"
>>char org="USAA Federal Savings Bank"
>>char fid="67811"
>>char serverAddr="https%3A%2F%2Fdf3cx-services.1fsapi.com
>> %2Fcasm%2Fusaa%2Faccess.ofx"
>>char appId="QMOFX"
>>char appVer="2300"
>>char headerVer="103"
>>char clientUid=""
>>int httpVMajor="0"
>>int httpVMinor="0"
>>char httpUserAgent="InetClntApp%2F3.0"
>> } #backend
>> } #data
>> -
>>
>> Notes:
>> -- 'httpUserAgent' is currently not configurable through GNC v4.4.1, but
>> it works when included in the file. It has been added in newer AqBanking,
>> look for support in next GNC release.
>> -- 'CLIENTUID' can be found in OFXLog.txt generated by Quicken. Signup
>> for trial and cancel within 30 days no charge.
>> -- 'your new USAA access id' can be found at
>> https://www.usaa.com/accessid
>>
>> You will need to disconnect accounts from within the AqBanking Wizard,
>> download accounts with new user configuration, then reconnect accounts. In
>> my case, the new credit card account numbers in the accounts list are not a
>> 100% match to the number found on your credit card. There were enough
>> common digits to know which was which, just be aware. I was able to
>> successfully download and update 2 checking accounts, a savings account,
>> and a credit card account.
>>
>> I hope this helps.
>>
>> Regards,
>>
>> Bob
>>
>> PS. I did clone the AqBanking repo and build and install the latest
>> libraries on the same machine I am running GNC. I am not sure if the
>> GNC used the libraries distributed with it or the ones I built so YMMV.
>> ___
>> gnucash-devel mailing list
>> gnucash-devel@gnucash.org
>> https://lists.gnucash.org/mailman/listinfo/gnucash-devel
>>
> ___
> gnucash-devel mailing list
> gnucash-devel@gnucash.org
> https://lists.gnucash.org/mailman/listinfo/gnucash-devel
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: [GNC-dev] [GNC] USAA FSB requires newer QWIN support
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 <
gnucash-devel@gnucash.org> wrote:
> I got new USAA OFX download working with GNC 4.4.1.
>
> It's mainly a configuration task.
>
> -- User config --
> int uniqueId=""
> char backendName="aqofxconnect"
> char userName=""
> char userId=""
> char customerId=""
> char country="us"
> char bankCode="314074269"
> int lastSessionId="0"
>
> data {
> backend {
> char bankName="USAA Federal Savings Bank"
> char org="USAA Federal Savings Bank"
> char fid="67811"
> char serverAddr="https%3A%2F%2Fdf3cx-services.1fsapi.com
> %2Fcasm%2Fusaa%2Faccess.ofx"
> char appId="QMOFX"
> char appVer="2300"
> char headerVer="103"
> char clientUid=""
> int httpVMajor="0"
> int httpVMinor="0"
> char httpUserAgent="InetClntApp%2F3.0"
> } #backend
> } #data
> -
>
> Notes:
> -- 'httpUserAgent' is currently not configurable through GNC v4.4.1, but
> it works when included in the file. It has been added in newer AqBanking,
> look for support in next GNC release.
> -- 'CLIENTUID' can be found in OFXLog.txt generated by Quicken. Signup
> for trial and cancel within 30 days no charge.
> -- 'your new USAA access id' can be found at
> https://www.usaa.com/accessid
>
> You will need to disconnect accounts from within the AqBanking Wizard,
> download accounts with new user configuration, then reconnect accounts. In
> my case, the new credit card account numbers in the accounts list are not a
> 100% match to the number found on your credit card. There were enough
> common digits to know which was which, just be aware. I was able to
> successfully download and update 2 checking accounts, a savings account,
> and a credit card account.
>
> I hope this helps.
>
> Regards,
>
> Bob
>
> PS. I did clone the AqBanking repo and build and install the latest
> libraries on the same machine I am running GNC. I am not sure if the
> GNC used the libraries distributed with it or the ones I built so YMMV.
> ___
> gnucash-devel mailing list
> gnucash-devel@gnucash.org
> https://lists.gnucash.org/mailman/listinfo/gnucash-devel
>
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: [GNC-dev] [GNC] USAA FSB requires newer QWIN support
I got new USAA OFX download working with GNC 4.4.1.
It's mainly a configuration task.
-- User config --
int uniqueId=""
char backendName="aqofxconnect"
char userName=""
char userId=""
char customerId=""
char country="us"
char bankCode="314074269"
int lastSessionId="0"
data {
backend {
char bankName="USAA Federal Savings Bank"
char org="USAA Federal Savings Bank"
char fid="67811"
char
serverAddr="https%3A%2F%2Fdf3cx-services.1fsapi.com%2Fcasm%2Fusaa%2Faccess.ofx"
char appId="QMOFX"
char appVer="2300"
char headerVer="103"
char clientUid=""
int httpVMajor="0"
int httpVMinor="0"
char httpUserAgent="InetClntApp%2F3.0"
} #backend
} #data
-
Notes:
-- 'httpUserAgent' is currently not configurable through GNC v4.4.1, but it
works when included in the file. It has been added in newer AqBanking, look
for support in next GNC release.
-- 'CLIENTUID' can be found in OFXLog.txt generated by Quicken. Signup for
trial and cancel within 30 days no charge.
-- 'your new USAA access id' can be found at https://www.usaa.com/accessid
You will need to disconnect accounts from within the AqBanking Wizard, download
accounts with new user configuration, then reconnect accounts. In my case, the
new credit card account numbers in the accounts list are not a 100% match to
the number found on your credit card. There were enough common digits to know
which was which, just be aware. I was able to successfully download and update
2 checking accounts, a savings account, and a credit card account.
I hope this helps.
Regards,
Bob
PS. I did clone the AqBanking repo and build and install the latest libraries
on the same machine I am running GNC. I am not sure if the GNC used the
libraries distributed with it or the ones I built so YMMV.
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel
