I just saw all the previous pages for this are down, and no longer exist.
Application Consent | USAA USAA quicken authentication codes etc They took them all down. On Sat, 2023-12-16 at 19:11 -0600, Daffy Duck wrote: > I am having the same error. Not sure how to get around it? > > What has been happening for a while is, I have to redo the authorization > every time I want to use gnucash to do direct connect. > > > > > > > -- > I have been having this issue since Dec 6 2023. I called USAA twice > (once each to tech support and banking), and was assured both times that > my account is still active. They escalated and came back with something > along the lines of -- keep trying it should start working again sometime... > > In the past, I would get the validation error in Chromium, but not in > Firefox. I now get that error in Firefox, Chromium on Linux, and on > Windows as well. > > I tested from a fresh test machine without any financial software, doing > the whole login process, and the error happens quite early, without any > interaction other than the browser authentication redirects, so I don't > see how it could be related to gnucash unless they have state cached on > their end to keep us locked out. > > Jon > > On 12/15/23 09:23, john wrote: > > > >> On Dec 14, 2023, at 20:43, John Haiducek <jhaiduce at gmail.com> wrote:>> > >> Downloading transactions from USAA accounts stopped working for me > >> today.>> In the past I've been able to restore access by following the > >> instructions>> at > >> https://wiki.gnucash.org/wiki/OFX_Direct_Connect_Bank_Settings#USAA and>> > >> getting an accessid from http://usaa.com/accessid or>> > >> https://df3cx-services.1fsapi.com/casm/usaa/enroll. However, now both of>> > >> those websites redirect to a page that returns the following in JSON:>> > >> {>> "error": "invalid_request",>> "error_description": "Validation > >> error">> }>> > >> Does anyone know a workaround for this? Is there an updated URL I can > >> use?> I had the same problem yesterday. I worked around it by downloading > >> a CSV of the transactions from the account and importing that instead.> > > It's possible that it's just a glitch that will get corrected in a few > > days. If not we'll need someone with Quicken and Wireshark to snarf the new > > secret handshake.> > > Regards,> John Ralls> > > > > _______________________________________________> gnucash-user mailing list> > > gnucash-user at gnucash.org > > To update your subscription preferences or to unsubscribe:> > > https://lists.gnucash.org/mailman/listinfo/gnucash-user > > -----> Please remember to CC this list on all your replies.> You can do > > this by using Reply-To-List or Reply-All. > > _______________________________________________ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user ----- Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
