I think I've found another quirk with respect to ofxDC and banks vs.
other institutions. Brokers with four digit <FIPID> tags tend not to
have <FID> tags. Vanguard and Ameritrade are among those that don't
have FIDs, but I have found some others that do. Aqbanking setup
insists that 'banks' have an entry in the FID slot. Ameritrade lets
me put the FIPID in the FID slot (apparently ignoring that slot on my
connections), and I can successfully retrieve transaction data from
Ameritrade.
Vanguard, however, does not accept the bogus FID info. If I try to
connect to Vanguard with the FID slot containing either the FIPID or
a space character, I get an html stream back in the ofx log saying
that the service is temporarily unavailable. However, if I use ofx.py
to connect both before and after my failed aqbanking attempt, I can
successfully connect to the same https address and retrieve data from
my account.
The Vanguard fidata entry indicates that the <OFXHEADER> is 200, but
it sends a 102 header back to ofx.py, so I don't think the ofx
version is the sticking point.
I discovered that some institutions are pickier than others with
respect to the header information sent in the ofx connection
negotiation. Chase refused my connections with a general 2000 error
when I had the ORG set to "Chase" instead of "B1". My experience with
other Vanguard security policies suggests that they are among the
pickiest (I get locked out of my account a couple times a year when
someone else thinks my ID is theirs and tries to log in 3 times in
one day -- not even sequentially, just 3 failures within a 24 hour
period.)
Is it feasible to allow either FID or Broker ID as the required data
for aqbanking setup? Broker ID is usually general text (vanguard.com
for example), so there might be a problem...
Dave
--
David Reiser
[EMAIL PROTECTED]
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Aqbanking-devel mailing list
Aqbanking-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aqbanking-devel