<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">I just saw a request for the OFX data
that Chase sends; here is a copy of the response I got from Chase
after trying (and failing) to download OFX data:<br>
<br>
response:<br>
OFXHEADER:100<br>
DATA:OFXSGML<br>
VERSION:102<br>
SECURITY:NONE<br>
ENCODING:USASCII<br>
CHARSET:1252<br>
COMPRESSION:NONE<br>
OLDFILEUID:NONE<br>
NEWFILEUID:20151210083844.000<br>
<br>
<OFX><SIGNONMSGSRSV1><SONRS><STATUS><CODE>15510<SEVERITY>ERROR<MESSAGE>Please
verify your identity within the next 7 days. Using your desktop
computer, go to your bankӳ website and visit the Secure Message
Center for
instructions.</STATUS><DTSERVER>20151210093848.702[-5:EST]<LANGUAGE>ENG<FI><ORG>B1<FID>10898</FI></SONRS></SIGNONMSGSRSV1><CREDITCARDMSGSRSV1><CCSTMTTRNRS><TRNUID>20151210083844.000<STATUS><CODE>15500<SEVERITY>ERROR</STATUS><CLTCOOKIE>1</CCSTMTTRNRS></CREDITCARDMSGSRSV1></OFX><br>
Completed<br>
<br>
Grabbed from the 'ofxlog.txt' file.<br>
<br>
-Mike<br>
<br>
<br>
On 12/10/2015 8:20 AM, Michael Wolfe wrote:<br>
</div>
<blockquote cite="mid:56698A38.5020503@gmail.com" type="cite">
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
<div class="moz-cite-prefix">As a side note, I am also having this
problem; I wasn't aware that there was something Chase was
expecting KMyMoney to send back.<br>
<br>
If anyone needs testing for a fix with Chase Bank, I'm available
to do so if there's a testing version available for Windows (or
alternatively some handholding with a code patch so I can build
it myself!).<br>
<br>
-Mike Wolfe<br>
<a moz-do-not-send="true" class="moz-txt-link-abbreviated"
href="mailto:wolfemi1@gmail.com">wolfemi1@gmail.com</a><br>
<br>
On 12/10/2015 4:53 AM, Thomas Baumgart wrote:<br>
</div>
<blockquote cite="mid:1921531.c3vgLc7Yct@thb-nb.site" type="cite">
<pre wrap="">Hi,
On Wednesday 09 December 2015 19:38:08 Jack wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Some of you may have seen some other posts I've made about this, but I
think I've tracked down the problem.
</pre>
</blockquote>
<pre wrap="">Thanks for the information. That helped a lot to identify what's going on.
</pre>
<blockquote type="cite">
<pre wrap="">Background: last month Chase credit cards made a "security enhancement"
change that has made all OFX downloads since 11/17 fail. The error
message says to got to the Chase secure message center for info on how
to verify your identity, but no such message ever appears. The section
at
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://wiki.gnucash.org/wiki/Setting_up_OFXDirectConnect_in_GnuCash_2#Chase_">http://wiki.gnucash.org/wiki/Setting_up_OFXDirectConnect_in_GnuCash_2#Chase_</a>
.22username_or_password_are_incorrect.22 indicates the need for using a UID
(user id) within the OFX request. It looks like they associate that user
UID with the account, probably to limit access. However, the first time
they see a UID on an OFX request, they should generate a PIN and send it to
your account at their Secure Message Center. You then use that PIN on
another page the message links to. I suppose since KMM isn't sending the
UID, they don't generate that message.
So - I don't see any place in KMM for a user UID. In fact, looking
into the libOFX source, I see the UUID type defined, but no element
defined as that type which looks like a user id. Can someone confirm
this is correct, and if so, does this need to be brought up on the
libOFX list before there is anything that KMM can do? (Other forum
messages I've seen seem to indicate that aqbanking can handle this, so
I'll see if I can get this set up, but I hate to spin my wheels if
someone can provide a more definitive answer.
</pre>
</blockquote>
<pre wrap="">I took a look into the OFX spec (version 2.1.1) and found chapter 2.5.1.1.1
"Client Unique ID <CLIENTUID>". In short, this is a uid generated by the
client (KMyMoney). Here's the paragraph of the spec (© 2006 Intuit Inc.,
Microsoft Corp., CheckFree Corp. All rights reserved):
---8<---
OFX servers can require OFX clients to include a client ID in each signon
request. This client ID should be unique to the installation of the client
software, but the method that the ID is generated is left up to the client.
The server can specify that this field is required using the <CLIENTUIDREQ>
tag in the applicable <SIGNONINFO> section of the profile. Servers should
expect that users may connect via OFX from multiple locations and may need to
associate more than one <CLIENTUID> value with their <USERID>.
---8<---
Would be interesting, if you see the CLIENTUIDREQ in the SIGNONINFO message of
the server. One can (at least could) enable logging for OFX traffic in some
way. Don't know, if that is still available. Will have to check.
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
KMyMoney-devel mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:KMyMoney-devel@kde.org">KMyMoney-devel@kde.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://mail.kde.org/mailman/listinfo/kmymoney-devel">https://mail.kde.org/mailman/listinfo/kmymoney-devel</a>
</pre>
</blockquote>
<br>
</blockquote>
<br>
</body>
</html>