Re: Automating US Bank Data Transfers

[Mike Wills <mike@xxxxxxxxxxxx>]

   They also support HTTPS, but I am sure that requires a key fob with a
   unique generated key ever 30 or 60 seconds, so I doubt that would work.
   SFTP (SSH), I could setup SSH, but am trying to avoid adding that to
   the system if other options work. FTPS (SSL), to which my question was
   asked. I looked again and they are saying FTPS SSL not SSH for the
   certificates. Most of the other options aren't feasible or I have no
   clue what they are talking about.

   So while I could script this, I won't be able to use FTPAPI for it?
   Just getting my ducks in a row.

   --
   Mike Wills
   [1]http://mikewills.me
   On Tue, Jul 3, 2012 at 3:40 PM, Scott Klement <[2]sk@xxxxxxxxxxxxxxxx>
   wrote:

     Hi Mike,
     Currently, FTPAPI does not support SSL at all.  This is mainly
     because I haven't had a use for it, myself.
     As someone who understands the network protocol internals, I think
     FTP over SSL is a kludge, and isn't especially secure. I would not
     recommend it unless you're given no alternative.
     Personally, I recommend using SFTP (SSH) instead.
     The note from US Bank that you cite also seems to be referring to
     SSH. (Though, I could be mistaken.) Typically, when you use SSL, you
     work with X.509 certificates, whereas they are referring to
     public/private keys. Granted, somewhere in the SSL certificate
     architecture, they're probably using public/private keys -- but when
     folks are referring to SSL, they don't usually use those terms.
     Whereas with SSH, public/private keys are the norm... so it seems
     likely that they are actually referring to SFTP (SSH).
     Maybe that's food for thought.
     But, if you are forced to use SSL/FTP, the IBM client does support
     it (to an extent, anyway) and you could potentially add SSL support
     to FTPAPI.  Or, you could purchase a 3rd party tool, such as the
     packages offered by Linoma (which look pretty nice to me...)
     -SK

   On 7/3/2012 2:10 PM, Mike Wills wrote:

       I am looking at what it would take to automate downloading the
   daily
       transactions from US Bank's lock box service. In asking for more
       details about downloading via FTPS (SSL) and how that is handled at
   the
       technical level so I can start planning what I need to do with
   Scott's
       FTPAPI, I get this:
       "US Bank will not be supporting password authentication in the near
       future, so the best bet is to use Public Key sign on authentication
       when we auto connect for the push."
       Does the API support that type of authentication? Has anyone worked
       with US Bank any type of automated transactions. What works well?
       --
       Mike Wills

         [1][3]http://mikewills.me
     References
         1. [4]http://mikewills.me/
     --------------------------------------------------------------------
     ---
     This is the FTPAPI mailing list.  To unsubscribe, please go to:
     [5]http://www.scottklement.com/mailman/listinfo/ftpapi
     --------------------------------------------------------------------
     ---

     --------------------------------------------------------------------
     ---
     This is the FTPAPI mailing list.  To unsubscribe, please go to:
     [6]http://www.scottklement.com/mailman/listinfo/ftpapi
     --------------------------------------------------------------------
     ---

References

   1. http://mikewills.me/
   2. mailto:sk@xxxxxxxxxxxxxxxx
   3. http://mikewills.me/
   4. http://mikewills.me/
   5. http://www.scottklement.com/mailman/listinfo/ftpapi
   6. http://www.scottklement.com/mailman/listinfo/ftpapi

-----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------