1

(4 replies, posted in Institution Comments)

As of about mid September 2021, something changed at T. Rowe Price and their OFX interface stopped working as noted here on OFX Home.  Over the last few months I called T. Rowe Price and did some further investigation that led to a solution for me using the PocketSense OFX scripts ( see sites.google.com/site/pocketsense/home/msmoneyfixp1 ).

    SiteName     : T. Rowe Price
    AcctType     : INVSTMT    #investment
    fiorg        : T. Rowe Price
    url          : https://api.public.troweprice.com/ffs-o … fx-request
    brokerid     : troweprice.com
    ofxVer       : 102
    appid        : QWIN
    appver       : 2700
    dtAcctUp     : 19900101

Cheers, David

As of about mid September 2021, something changed at T. Rowe Price and their OFX interface stopped working as noted here on OFX Home.  Over the last few months I called T. Rowe Price and done further investigation that led to a solution for me using the PocketSense OFX scripts ( see sites.google.com/site/pocketsense/home/msmoneyfixp1 ).

    SiteName     : T. Rowe Price
    AcctType     : INVSTMT    #investment
    fiorg        : T. Rowe Price
    url          : https://api.public.troweprice.com/ffs-o … fx-request
    brokerid     : troweprice.com
    ofxVer       : 102
    appid        : QWIN
    appver       : 2700
    dtAcctUp     : 19900101

Cheers, David

In mid-November 2021, Fidelity changed their FI Url to https://nbofx.fidelity.com:443/netbenefits/ofx/download
Cheers, David

Problem solved.  I upgraded to Python 2.7.15 which supports OpenSSL TLSv1.2.  Now the PocketSense python scripts successfully download banking and investment transactions from the USAA OFX server.  Cheers, Simada

Thanks Jesse, I will contact USAA.  Meanwhile I tried to troubleshoot the error message and found that it may be related to an effort to remove weak cryptographic standards such as TLSv1/TLSv1.1.  Some internet sites such as GitHub <https://githubengineering.com/crypto-removal-notice/> are forcing an upgrade to TLSv1.2,  and clients using the older standards now get this error message.  Don't know that it applies to USAA but I will feed back what I find.
Cheers, Simada

About two weeks ago my OFX connection to USAA banking and investment accounts began failing.  Here on OFXHome, it shows that USAA is Validated successfuly as of 180625. However, when I try Ofxget, it fails too.  So I suspect there is a problem.

I use PocketSense Python Scripts to download OFX transaction data into MS Money Sunset edition.  Here is the message I get when I try to download transactions:

USAA FEDERAL SAVINGS BANK : 00XXXXXXXX : Getting records since:  20180610
** An ERROR occurred sending POST request to service2.usaa.com
   Exception type  : <class 'ssl.SSLError'>
   Exception val   : [Errno 1] _ssl.c:499: error:1407742E:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert protocol version

USAA IMCO MUTUAL FUNDS : 000XXXXX : Getting records since:  20180610
** An ERROR occurred sending POST request to service2.usaa.com
   Exception type  : <class 'ssl.SSLError'>
   Exception val   : [Errno 1] _ssl.c:499: error:1407742E:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert protocol version

Any thoughts on how to solve this problem?
Thank you.  Simada