Re: [GNC] USAA OFX Direct Connect stopped working

2023-12-16 Thread Daffy Duck
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  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.


Re: [GNC] USAA OFX Direct Connect stopped working

2023-12-16 Thread Daffy Duck
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  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.


Re: [GNC] Nice to Have?

2023-12-16 Thread R Losey
I think that I always have seen the full list of scheduled transactions (on
an iMac using 5.3) when GC starts; most of them are empty; some have
Reminder or Created tags. But I thought I always see the full list.

On Thu, Dec 14, 2023 at 2:45 PM Adrien Monteleone <
adrien.montele...@lusfiber.net> wrote:

> This is weird.
>
> I managed to trigger this complete listing, but now I can't fix it back.
>
> At first, my Since Last Run (SLR) showed only a list of reminders and
> created SX.
>
> After playing with the option to remind in advance, unticking it removed
> that SX as expected as it wasn't yet time to fire.
>
> But setting it back, and re-running the SLR, now all Enabled SX are
> listed (below the Reminders unlike Grace's screenshot) and I can't seem
> to make them go away and get back to the original behavior.
>
> Regards,
> Adrien
>
> On 12/14/23 2:35 PM, Adrien Monteleone wrote:
> > It looks like that is what Grace is already referring to by the
> screenshot.
> >
> > I'm not even sure how to show all SX on that dialog, even those not set
> > to remind or auto-create yet.
> >
> > If I set a window or untick the option entirely, they don't show up.
> >
> > If there are none for the day, I get that notice instead of a list.
>
> ___
> 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.
>


-- 
_
Richard Losey
rlo...@gmail.com
Micah 6:8
___
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.


[GNC] (no subject)

2023-12-16 Thread was698002 via gnucash-user
 Can confirm that error persists as of 12/16/2023 and says- 
>We're unable to complete your request. To download USAA account transactions 
>into Quicken, you'll need to verify your information. Get Access ID and PIN 
>here https://df3cx-services.1fsapi.com/casm/usaa/enrol 
and that clicking that address results ib-
    
error    "invalid_request"
error_description    "Validation error"
Henry

  1. Re:  USAA OFX Direct Connect stopped working (john)


--

Message: 1
Date: Fri, 15 Dec 2023 09:23:32 -0800
From: john 
To: John Haiducek 
Cc: GNU Cash User 
Subject: Re: [GNC] USAA OFX Direct Connect stopped working
Message-ID: <2db4db9d-381e-48f5-b909-416ef04c0...@ceridwen.us>
Content-Type: text/plain;    charset=us-ascii



> On Dec 14, 2023, at 20:43, John Haiducek  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


  

|  | Virus-free.www.avast.com |

___
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.


[GNC] Online Banking

2023-12-16 Thread david amaral via gnucash-user
I am attemting to set up online banking to Fidelity and not having much luck. I 
keep getting error of "bad request"  Have no idea as to why,
AqBanking v6.5.4.0stableSending jobs to the bank(s)Sorting commands by 
accountSorting account queues by providerSend commands to providersSend 
commands to provider "aqofxconnect"Locking customer "7"Sending 
request...Connecting to server...Resolving hostname "ofx.fidelity.com" ...IP 
address is "23.209.84.151"Connecting to "ofx.fidelity.com"Connected to 
"ofx.fidelity.com"Connected.Sending message...Message sent.Waiting for 
response...Receiving response...HTTP-Status: 400 (Bad Request)Unlocking 
customer "7"
Any help would be greatly appreciated

___
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.


Re: [GNC] USAA OFX Direct Connect stopped working

2023-12-16 Thread Jonathan Knepher via gnucash-user
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  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@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.