Let's say you have trading partners who can only transfer files to you via SFTP. Incidentally, you also happen to have an account on Azure Blob Storage and you prefer to store those files there. You're probably thinking: How can I automatically copy files from my SFTP server to Azure Blob Storage? That's easy if you're using JSCAPE MFT Server.

JSCAPE MFT Server makes it easy to strengthen secure file transfers with OpenPGP encryption and decryption. But before you can protect your files with this cryptography method, you need to create the necessary public/private key pairs. In this post, we'll introduce you to three ways of doing that.

Overview

In this post, you'll learn how to set up a HTTPS file transfer. We'll begin with a Quick Start, where you'll use the default settings in order to get a HTTPS file transfer service up and running with just a few clicks. After that, we'll tackle some of the more advanced settings so you can choose your desired set of SSL/TLS cipher suites and server key. Your choice of cipher suites and keys will have an effect on the security of your HTTPS file sharing and its compatibility with your users' web browsers.

Overview

A couple of weeks ago, we compared the advantages and disadvantages of using Amazon S3 and local storage as file storage system for JSCAPE MFT Server. For those who want to try storing their file transfer server end user files on Amazon S3, this post is for you.

When you first launch your web file transfer service on JSCAPE MFT Server, you'll notice that the web user interface has the JSCAPE branding starting from the login screen and continuing inside. You can actually customize that and make it your own.

When I first read about HSTS, my first reaction was, "What's this? A replacement for HTTPS? Considering the ubiquity of HTTPS, shouldn't we be working to improve it first instead of replacing it?" Turned out, my initial understanding of HTTP Strict Transport Security was off the mark.

Of all file transfer services out there, perhaps the easiest is using HTTP/S as a file transfer service, aka a web file transfer service. That's because users don't have to install anything. They'll only need to upload or download files from your service for a web browser. If you're using JSCAPE MFT Server, setting up an HTTP/HTTPS file transfer service is easy as well.

JSCAPE is a managed file transfer protocol solution that supports any protocol and any platform. Fully scalable and flexible, JSCAPE's managed FTP server enables users to handle multiple protocols (FTPS, SFTP, AS2 and OFTP, as well as SSH and SSL/TLS) from a single server. This makes it possible to simplify enterprise file transfers, improve compliance with two-factor authentication

With JSCAPE, users can meet any enterprise file sharing needs, including HTTP file transfers. Let me show you how it's done.

As you scout for the most cost-effective way of transmitting files with your business units and trading partners, among the many file sharing solutions that will likely stand out are free FTP servers. Most of these software applications are already bundled (or readily available through repositories) in operating systems like Linux, Mac OS X and Microsoft Windows, so they likely don't require additional costs ... or so it seems.

Not everyone using your web file transfer server needs to have a user account. There can be instances when it's perfectly fine for a user to just carry out an anonymous file upload. Meaning, that user doesn't have to login. This set up can be useful in cases where an outsider just needs to do a one-off upload. We'll show you how to enable that functionality on JSCAPE MFT Server.

Overview

PGP encryption can add another layer of protection to a trading partner file transfer already secured by FTPS. It can also provide data-at-rest encryption as soon as the file arrives at the other end. In this post, we'll show you how to set up a fully automated file transfer secured by OpenPGP and FTPS using JSCAPE MFT Server triggers.