
- #FILEMAKER SERVER 14 SSL CERTIFICATE PRO#
- #FILEMAKER SERVER 14 SSL CERTIFICATE SOFTWARE#
Database Server test: Use FileMaker Pro to connect to a hosted file and check the security lock icons in the bottom-left corner of the window.This is your server’s custom SSL certificate. Multi-machine deployments: Run these commands on each machine in the deployment to import each matching certificate, then restart FileMaker Server on all machines.Īfter importing the certificate, a file named serverCustom.pem should be created in /FileMaker Server/CStore. Click Save at the bottom of the Admin Console window.Enable "Use SSL for database connections".Go to the Admin Console ( Database Server > Security.Run the import command via command prompt:.The certificate should be in Base64 PEM format. Only the server certificate needs to be imported. Import the certificate into FileMaker ServerĪfter the purchase, you will recieve an email from the CA containing your server certificate (matching your domain name) and additional intermediate certificates. Multi-machine deployments: Use each machine’s CSR to purchase a separate certificate for each machine. Validate by email that you are the owner of the domain name specified in the CSR.
#FILEMAKER SERVER 14 SSL CERTIFICATE SOFTWARE#
Select "Other" as the server software used to generate the CSR. Select a signature hash algorithm (use SHA-2 with SHA-1 root).
(Including -Begin Certificate Request- and -End Certificate Request-)
Paste or upload the contents of your CSR: Open serverRequest.pem in a text editor and copy the entire contents into the space provided on the CA’s website. To complete the purchase, you may be asked to do the following: The following certificates are supported in FileMaker Server 14 and earlier: Select a supported SSL certificate to purchase from a Certificate Authority (CA). Multi-machine deployments: Go to each machine in the deployment and run the commands to create a CSR for each machine. serverKey.pem: private key file required for the certificate import process. serverRequest.pem: CSR required for the SSL purchase process. This will create the following files in /FileMaker Server/CStore/ : Windows: Open Command Prompt (cmd) as an administrator and run the commands:Ĭd “C:\Program Files\FileMaker\FileMaker Server\Database Server”. macOS: Open Terminal and run the command:. When purchasing a SSL certificate, the CSR tells the Certificate Authority what domain to issue the certificate for. When you purchase a new domain, you may recieve a new email account through the DNS registrar that you can use to validate that you are the owner of the domain.Ī create a certificate signing request (CSR) is a hash file containing information about your domain, including the domain name, company, etc. For multi-machine deployments, each machine should have its own domain or subdomain. If you already own a domain, you may instead purchase a subdomain (such as ) instead of getting an entirely new domain. Please keep the following points in mind: To obtain a FQDN, you must register your unique domain name with a DNS registrar who keeps the domain in sync with your server's IP address.
Your Fully Qualified Domain Name (FQDN) is the public-facing address that you would like to use to access FileMaker Server. Purchase a Fully Qualified Domain Name (FQDN)
Follow the process in this article to obtain a new certificate or replace an expired certificate. The standard FileMaker SSL certificate installed by default is available for test purposes only. If security is important to your operations, all machines running FileMaker Server should have a custom SSL certificate.