mirror of
https://github.com/aclindsa/ofxgo.git
synced 2024-11-23 11:40:05 -05:00
01b26887af
Section 4.2.2.2 Type 1 Protocol Overview in the [Open Financial Exchange Specification 2.2, Nov 26, 2017](https://www.ofx.net/downloads/OFX%202.2.pdf) states that: Type 1 applies only to the request part of a message; the server response is unaffected. Thus it appears that we can safely parse SECURITY:TYPE1 using the same logic that we parse SECURITY:NONE As I understand it, Security:TYPE1 indicates that the financial institution uses SSL enryption to protect customer credentials in transit. This applies explicitly to the incoming requests which may contain authentication as part of the request but does not appear to cause any material changes to the response format. As a result it appears that we can safely parse SECURITY:TYPE1 responess in the same way that we parse SECURITY:NONE responsese. |
||
---|---|---|
.. | ||
401k_v203.ofx | ||
inv_v202.ofx | ||
ira_v202.ofx | ||
moneymrkt1_v103_TYPE1.ofx | ||
moneymrkt1_v103.ofx | ||
moneymrkt1_v203.ofx |