Let’s begin!įor those who are new to SSL or need a refresher, let’s start by defining some of the basic concepts, terms, and reasons behind SSL (if you just want to get to the steps, scroll down a little further). As mentioned, if your server is in-house this article still applies to you, but you can skip the Azure specific stuff. The certificate will be installed on both FileMaker Server and Windows Server in order to enable encrypted connections directly to FileMaker Server and also to web pages hosted on Windows Server! I will focus on using a Wildcard SSL certificate, but the same process can be used for installing a single domain certificate. This article is intended to be a deep dive, step by step, “how to” article walking through the process of setting up a Wildcard SSL certificate in FileMaker server and Windows server in the Azure cloud (if your Windows Server is not in the Azure cloud, most of this article will still apply and be useful). Why: Security is a priority with any solution, but especially if you connect to your server over a WAN (as opposed to your local network).
With: FileMaker 16+ (these instructions will likely work with past versions as well).What: How to Install a Wildcard SSL on Windows Server in Azure.Who: Anyone interested in securing your Azure cloud server with SSL (Wildcard or single domain).
0 kommentar(er)
