[Kmymoney-devel] [kmymoney4] [Bug 315760] Unable to map to and online accounts at Capital One Bank

[Thomas Baumgart]

https://bugs.kde.org/show_bug.cgi?id=315760

--- Comment #34 from Thomas Baumgart <ipwizard at users.sourceforge.net> ---
Looks like we're getting a bit closer to a solution of the problem as I now
understand the problem. I found a discussion over at our friends at GnuCash:
http://lists.gnucash.org/pipermail/gnucash-devel/2012-December/034626.html and
a possible solution
http://lists.gnucash.org/pipermail/gnucash-devel/2013-March/035110.html which
refers to a blog post at
http://pocketsense.blogspot.de/2013/01/jan-2013-version-of-scripts-available.html.

So it seems, we need a ClientUID field to transfer to the bank. Don't know if
this is per KMyMoney instance, per account or what. Martin of aqBanking fame
seems to have the same problem in understanding:
http://lists.gnucash.org/pipermail/gnucash-devel/2012-December/034630.html .

Here's what the OFX spec says:

<OFXSPEC version="2.1.1" chapter="2.5.1.1.1">
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>.
The client may make this value user discoverable, so that the user can register
the client ID with financial institutions.
</OFXSPEC>

The spec even has an example for it in chapter 2.5.6 entitled "Signon in OFX
2.1.1 which includes CLIENTUID and both additional credential tags" which
contains the following section:

<APPID>MyApp</APPID>
<APPVER>1600</APPVER>
<CLIENTUID>22576921-8E39-4A82-9E3E-EDDB121ADDEE</CLIENTUID>
<USERCRED1>MyPin</USERCRED1><!--Profile has included
<USERCRED1LABEL>PIN:</USERCRED1LABEL>-->
<USERCRED2>MyID</USERCRED2><!--Profile has included
<USERCRED2LABEL>Your ID:</USERCRED2LABEL>-->

This somehow goes along with the error, that the device is not authorized.

-- 
You are receiving this mail because:
You are the assignee for the bug.