SSL/TLS on FileMaker Server
IntermediateInstall and manage SSL certificates on FileMaker Server to encrypt data in transit between clients and the server.
What you'll learn
- Why SSL/TLS matters for FileMaker Server
- The difference between a self-signed and a CA-signed certificate
- How to install a certificate on FileMaker Server
- Certificate renewal and why automation matters
SSL/TLS encrypts data between FileMaker clients and FileMaker Server. Without it, account credentials and data travel in plaintext across the network. Every production FileMaker Server should have a valid SSL certificate -- both for security and because clients receive browser-style security warnings without one.
Why SSL is required for production
Without SSL: FileMaker account credentials pass in plaintext during authentication (observable on any network path between client and server), Data API calls are unencrypted, and WebDirect pages deliver data over plain HTTP. FileMaker Server ships with a self-signed certificate that enables encryption but triggers security warnings in browsers and some clients.
Sign in to track your progress and pick up where you left off.
Sign in to FM Dojo