Scroll

What are the FTP System Requirements?

 

**Medidata is no longer implementing SFTP

What are the advantages of FTPS:

  • Better security
  • Better flexibility
  • SFTP uses unsigned and unverified encryption keys rather than certificates. This means that it can't take advantage of the "chains of trust" paradigm facilitated through Certificate Authorities; no third party verification of remote entity, and no requirement for periodic revalidation of the security information.
  • Standard Network Ports.

No need to open additional ports in firewalls since FTPS uses the same ports as FTP.

 

Connection notes

 

Server control port

 

  • Normally the FTP control connection should be configured to use port 21 however some firewalls treat port 21 specially and may interfere with the TLS negotiation or transfer of files. To circumvent this interference port 990 is provided as an alternative to port 21. This is not an implementation of “FTP using Implicit SSL” but an alternate instance of Secure FTP that can be used if TLS negotiation on port 21 is not working correctly.

Data port range

 

  • The usual data transfer connection method is to use passive mode data transfers in which the FTP client connects to the FTP server to retrieve files and directory listings. Because the TLS encryption obscures the data transfer port information from the firewall it is usually necessary to explicitly permit outbound connections from the client’s system to the FTP server. To facilitate this data ports are always selected from the range 12000 to 12100 inclusive

 

Certificate information

The certificates used to secure the communications with Medidata’s FTP servers are described below.

If your FTP client software requests you verify the certificate used on a particular connection, which may occur the first time you connect to a particular site, the information below can be used to verify it matches with the certificate displayed by your FTP client.

Most FTP clients will allow you to check a box when validating the certificate so that it will be accepted automatically for future connections.

 

Certificate for ftp01.ftp.mdsol.com

The certificate for the production FTP server is dedicated to that purpose and will normally not raise any alerts but the information below may be used to verify the connection is indeed to Medidata’s FTP service.

 

Certificate for ftp03.ftp.mdsol.com

The certificate for the non-production FTP server is dedicated to that purpose and will normally not raise any alerts but the information below may be used to verify the connection is indeed to Medidata’s FTP service.

 

Certificate for ftp04.ftp.mdsol.com

The certificate for the legacy FTP server is dedicated to that purpose and will normally not raise any alerts but the information below may be used to verify the connection is indeed to Medidata’s FTP service.

 

Certificate for other Medidata FTP servers

Other Medidata FTP services use a “wildcard” certificate to secure the communications channels. Some FTP clients will display an alert concerning an "untrusted certificate" or “invalid certificate” when connecting. The reason for this is the name in the certificate (*.mdsol.com) does not match the hostname according to the strictest interpretation of the TLS guidelines. The certificate must be accepted if the connection is to be used, so you should verify the fingerprint of the certificate displayed by your software matches one of the certificates in this section.

 

User name and password are provided to you by email.



Validated client software

The following FTP client software was used during the validation process for the current FTP server deployments. It does not indicate a preference or requirement for these clients over any other or for these particular versions over any other.

For the Medidata FTP servers named ftp01.ftp.mdsol.com or ftp04.ftp.mdsol.com: Core FTP LE 2.1 or later

Fetch 5.3 or later Filezilla 3.3 or later

Globalscape Cute FTP 8 Professional or later Ipswitch WS_FTP Professional 2007 or later lftp 3.5.1 or later

 

For other Medidata FTP servers (ftp02.ftp.mdsol.com, ftp03.ftp.mdsol.com and others): Core FTP LE 2.1 or later

Fetch 5.3 or later

Filezilla 3.0.9 or earlier only (3.0.10 and later are known to not work)

Globalscape Cute FTP 8 Professional or later Ipswitch WS_FTP Professional 2007 or later lftp 3.5.1 or later

 

Following these steps should solve your issue. If it hasn’t, please call our Help Desk.

 

TIP: We are always working on ways to make our products work better for you, so remember to “follow” this article so when new solutions are posted, you’ll get an email alerting you!

 

Thank you for using Medidata’s Help Center!

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments: 0