Azure Data Lake is an excellent option for storing massive amounts of unstructured, semi-structured, and structured data in the cloud. One of the queries we often get pertaining to it is how to push files from a local storage to Azure Data Lake based on an event. Let me show you how it's done using JSCAPE MFT Server.

In a previous post, we taught you how to automatically transfer files from SFTP to Azure Blob Storage using a JSCAPE MFT Server network storage object. This time, we'll show you how to do it using a trading partner object.

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 a previous post, we talked about typical situations that call for server to server file transfers. We’re pretty sure some of you want to know how they’re actually set up, so we came up with this blog post. In this article, we’ve outlined all the necessary steps you need to take to set up a server to server file transfer.

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.

An Overview of HMAC

Data integrity checks are vital to secure communications. They enable communicating parties to verify the integrity and authenticity of the messages they receive. In secure file transfer protocols like FTPS, SFTP, and HTTPS, data integrity/message authentication is usually achieved through a mechanism known as HMAC (Hash-based message authentication code). In this post, we explain what HMAC is, its basic inner workings, and how it secures data transfers.

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.