new (inconsistent) OFX import problem (no clientuid)
Jack
ostroffjh at users.sourceforge.net
Mon Mar 2 19:34:36 GMT 2020
The change is that now KMM does not include the CLIENTUID in the ofx
request, which is absolutely required by Chase. That error message is
simply a side effect of how Chase handles the request. Don't bother
checking the secure message center, no message will ever be created.
What I don't understand is how the change Thomas made to how cmake finds
libofx still allows libofx to be found, but messes up an #include in the
test program to check for the CLIENTUID code within libofx. It can't
find /libofx/libofx.h (when it should be looking for libofx/libofx.h
without the leading slash) but the assumption is just that you have a
version of libofx without the needed code. That change was made only a
few days ago, so it only affects versions built since then, and since
the overall build still succeeds, the problem will only be noticed by
folks using ofx to fetch from institutions that absolutely require the
clientuid, such as Chase.
On 3/2/20 1:44 PM, Brendan Coupe wrote:
> I was going to say that I have been downloading a Chase credit card
> successfully for a while without any issues. I just tried it this
> morning and it no longer works.
>
> I'm running Fedora 31 and compiled from the master branch in the last
> couple of days. libofx is version 0.9.13-3.fc31.
>
> This is the error messages that I received:
>
> Unable to import '/tmp/kmymoney.xxxxxx' using the OFX importer plugin.
> The plugin returned the following error:
>
> SONRS: Unknown code (Code 15510): The description of this code is
> unknown to libOfx (Please verify your identity within the next 7 days.
> Using your desktop computer, go to your bank�s website and visit the
> Secure Message Center for instructions.)
>
> CCSTMTTRNRS: Signon invalid (Code 15500): The user cannot signon
> because he or she entered an invalid user ID or password.
>
> I switched back to a version of KMM that I compiled in 2020.02.19 and
> I don't have a problem downloading from Chase. it appears something
> may have changed in KMM in the past couple of weeks to cause this
> issue.
>
> ----
> Brendan Coupe
>
> On Mon, Mar 2, 2020 at 10:59 AM Jack <ostroffjh at users.sourceforge.net> wrote:
>> On 2020.03.02 11:35, Jack wrote:
>>> Good morning,
>>>
>>> Yesterday, I tried to import (libofx) two Chase accounts I have not
>>> done in a long time, and got the dreaded message about needing to go
>>> to their website secure message center to validate my access. Long
>>> story short, it has nothing to do with the bank, but it seems my
>>> current build of KMM (from 5.0 git head) does NOT include the ofx
>>> client uid feature. I've tried several cmake lines, and it always
>>> finds libofx, but sometimes fails the test for the clientuid
>>> functionality. My current libofx is 0.9.15, which was installed 15
>>> October. What I find most peculiar is that I cannot seem to find the
>>> difference between different builds that one finds the client UID
>>> stuff, and another does not. I can generally get success with a
>>> manual build, but not with the Gentoo ebuild that uses 5.0 git head.
>>> I'll continue to dig further, but wonder if anyone else has seen this
>>> or has any thoughts on what I should be looking for.
>>>
>>> As always, thanks for any suggestions.
>>>
>>> Jack
>> Got a response to my post on the Gentoo forums - pointing to commit
>> https://cgit.kde.org/kmymoney.git/commit/?id=487f8758987edb72e616a602706f100cafa877d8
>> (that's in master, but was cherry-picked to 5.0) although I'm not sue I
>> see exactly how that change caused the problem.
>>
>> Jack
More information about the KMyMoney-devel
mailing list