[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [kmymoney4] [Bug 315760] Unable to map to and online accounts at Capital One Bank
From:       utwes <utwes () hotmail ! com>
Date:       2013-03-19 19:17:01
Message-ID: bug-315760-17878-Lxd2rSuO8o () http ! bugs ! kde ! org/
[Download RAW message or body]

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

--- Comment #35 from utwes <utwes@hotmail.com> ---
(In reply to comment #34)

Thomas - thank you so much for your help in tracking down additional resources.
 I agree that the GNUCash posts seem to most closely resemble our challenge,
and it makes sence that the bank would accept a GUID to determine "unique
devices".

In regards to your comments below and based on the comments on the discussion
boards, it seems that if we were able to add the CLIENTID tag to the OFX
request, that might solve our issue.  However, I'm assuming that isn't
something that I can do on my side (modifying .kmy file or otherwise).  In
fact, it might be something that KMM developers will depend on AQBanking to do,
but please let me know if there are next steps here.

Thanks.

[snip]
> 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 watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]