JIRA

  • Log In Access more options
    • Online Help
    • GreenHopper Help
    • Agile Answers
    • Use Agile By Default
    • Keyboard Shortcuts
    • About JIRA
    • JIRA Credits
    • What’s New
  • Dashboards Access more options (Alt+d)
  • Projects Access more options (Alt+p)
  • Issues Access more options (Alt+i)
  • Agile Access more options (Alt+g)
  • Create Issue
  • Mule
  • MULE-4048

FTPS transport

  • Agile Board
  • More Actions
  • Views
    • XML
    • Word
    • Printable

Details

  • Type: New Feature New Feature
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: 2.1.1
  • Fix Version/s: Product Backlog
  • Component/s: Transport: FTP / SFTP
  • Labels:
    None
  • User impact:
    Low
  • Similar Issues:
    None

Description

Actually Mule can't make FTPs, but we worked on this and finally made it !
If you're interesting in it, upgrade commons-net to 2.0 for having the FTPSClient (for now in Mule it's 1.4.1).
Then in org.mule.transport.ftp.FtpConnectionFactory put in comment client.setReaderThread() in activateObject() and passivateObject().
After that we need new parameters, like "ftps" (true or false), "proctol" (SSL or TLS), and "implicit" (true or false). Those parameters should be added to the ftp xsd. After that, in FtpConnectionFactory.makeObject(), just add something like this to create the client :

FTPClient client;

if(isFtps()) { client = new FTPSClient(ftpsProtocol, ftpsImplicit); } else { client = new FTPClient(); }

Everything works fine for us, so if you have any questions just ask

Activity

Ascending order - Click to sort in descending order
  • All
  • Comments
  • Work Log
  • History
  • Activity
  • Transitions
  • Commits
  • Source
  • Builds
Andrew Perepelytsya made changes - 15/Dec/08 09:15 AM
Field Original Value New Value
Priority To be reviewed [ 6 ] Major [ 3 ]
Summary making FTPs  FTPS transport
Daniel Feist made changes - 16/Dec/08 11:39 AM
Fix Version/s 2.x Product Backlog [ 10440 ]
Issue Type Improvement [ 4 ] New Feature [ 2 ]
Ken Yagen made changes - 16/Dec/08 03:32 PM
Link This issue relates to EE-249 [ EE-249 ]
Hide
Permalink
Laurent GARCIA added a comment - 29/Dec/08 06:32 AM

I found a server where I got the reply "550 PROT P required" during the FTPSClient.listFiles() command.
I seek and finnaly found that we need to call FTPSClient.execPROT("P") after the connection.
In the javadoc of commons-net there is :
execPROT :
Data Channel Protection Level :
C - Clear
S - Safe(SSL protocol only)
E - Confidential(SSL protocol only)
P - Private
So I add a parameter prot to my connector and check if the value is correct before calling the method.

The parameter "prot" should be added too in the ftp xsd, and the execPROT() called after the connection sucessed if "prot" is not null.

Show
Laurent GARCIA added a comment - 29/Dec/08 06:32 AM I found a server where I got the reply "550 PROT P required" during the FTPSClient.listFiles() command. I seek and finnaly found that we need to call FTPSClient.execPROT("P") after the connection. In the javadoc of commons-net there is : execPROT : Data Channel Protection Level : C - Clear S - Safe(SSL protocol only) E - Confidential(SSL protocol only) P - Private So I add a parameter prot to my connector and check if the value is correct before calling the method. The parameter "prot" should be added too in the ftp xsd, and the execPROT() called after the connection sucessed if "prot" is not null.
Ken Yagen made changes - 29/Dec/08 04:20 PM
Link This issue relates to EE-249 [ EE-249 ]
Hide
Permalink
Lee Faus added a comment - 11/May/11 09:43 AM

We need support for FTPS where the customer is currently running on a Windows machine. Since .NET does not really have an SSH dll, FTPS is their only real option. We need support for TLS/SSL over FTP. I would envision a simple FTP transport extension that supports an SSL cert and you can expand the transport to include the key-location and if the key does not exist, it will default to TLS.

Show
Lee Faus added a comment - 11/May/11 09:43 AM We need support for FTPS where the customer is currently running on a Windows machine. Since .NET does not really have an SSH dll, FTPS is their only real option. We need support for TLS/SSL over FTP. I would envision a simple FTP transport extension that supports an SSL cert and you can expand the transport to include the key-location and if the key does not exist, it will default to TLS.
Hide
Permalink
Mohamed Elshami added a comment - 26/Apr/12 04:41 AM

Hi Lee,

Any updates with the FTPS support? I am using Mule EE 3.1.3, still unable to get FTPS to work. I've tried using my own FTPConnectionFactory derived from org.mule.transport.ftp.FtpConnectionFactory, but still having problems getting FTPSClient to work.

If you guys have already implemented that would be great.

Regards,
Mohamed

Show
Mohamed Elshami added a comment - 26/Apr/12 04:41 AM Hi Lee, Any updates with the FTPS support? I am using Mule EE 3.1.3, still unable to get FTPS to work. I've tried using my own FTPConnectionFactory derived from org.mule.transport.ftp.FtpConnectionFactory, but still having problems getting FTPSClient to work. If you guys have already implemented that would be great. Regards, Mohamed
This list may be incomplete, as errors occurred whilst retrieving source from linked applications:
  • Repository mule on http://foo.bar/ failed: Error in remote call to 'FishEye 0 (http://foo.bar/)' (http://foo.bar) [AbstractRestCommand{path='/rest-service-fe/changeset-v1/listChangesets/', params={expand=changesets[-21:-1].revisions[0:29], comment=MULE-4048, p4JobFixed=MULE-4048, rep=mule}, methodType=GET}] : java.net.UnknownHostException: foo.bar

People

  • Assignee:
    Unassigned
    Reporter:
    Laurent GARCIA
Vote (13)
Watch (10)

Dates

  • Created:
    15/Dec/08 09:10 AM
    Updated:
    26/Apr/12 04:41 AM

Agile

  • View on Board
  • Atlassian JIRA (v5.0.7#734-sha1:8ad78a6)
  • Report a problem
  • Powered by a free Atlassian JIRA open source license for MuleForge. Try JIRA - bug tracking software for your team.