In an effort to figure out how SSL works with filemaker I have enabled the default SSL cert that comes with filemaker. Unfortunately I am still presented with an SSL error when I connect to the databases hosted on the server (see image). What steps am I missing in order to get this certificate to work? I understand this is a "not for production" certificate however it is in date and valid and we are using it to see how a production installation would be achieved. FM Server 16, FMPro 16 Windows server 2012.
In order to reproduce the error we:
1. Enabled SSL on the FM server
2. Restarted the service
3. Checked SSL certificate in FM admin console
4. Connected to server using client
Any help appreciated.
We are running FM server 16 with FM pro 16 and FM Go 16 clients. We have do not use SSL certs as yet. When opening databases on the go client, the user is presented with a dialog stating that the connection is not secure and would they like to proceed. Secondly, programmatic access to the server is failing due to this new error being returned from the first "ping" of the server. I understand this is normal behaviour but obviously we want to get rid of this.
We need to sign our server. The problem is that it is used on the intranet only and CA's will not sign machines that are not public facing. We will not be making our server public facing.
What are the best practices surrounding getting this machine certified?
Any help appreciated.
I've done a search in this forum for "SSL" and it returns no result. So I'll start this thread:
Has anyone posted a step by step guideline on how to implement SSL for FileMaker Server? If not, it would be very helpful, at least for me.
I am familiar with generating the request from the FileMaker Server Admin Console. I am familiar with submitting the generated pem key to the GoDaddy service, who then generates a certificate for a price. I am familiar with placing said certificate in the correct folder on the server. However, that's where I leave off. There's some final steps missing, I don't know what they are. But we need to somehow "connect" the domain name we submitted when buying the certificate (www.something.com) , to the actual server we are using (it only has a static IP address), somehow. No idea what those steps would be. Any insight would be appreciated.
What is Code-X?
Code-X is a free FileMaker Developer Tool that lets you restrict features within your own demo FileMaker Solutions and unlocking them for paying customers with license codes.
We used to charge AU$450 (US$350) for Code-X but are now giving it away for free to the FileMaker community.
So what can you do with Code-X?
Add 30-day trial periods Restrict features within your demo solutions Limit the number of records unregistered users can create Limit the number of users that can use your solution Create different tiered licenses such as Basic and Pro Add nag dialogs to prompt unregistered users to register Lock your paid solution to a device to prevent piracy Generate and issue license codes that unlock your FileMaker solutions for paying customers More Information
To download the latest version, or for more information visit:
FileMaker Developer Tool - Code-X
Code-X was developed by Hi-Voltage, you can visit our site here:
FileMaker Programer Melbourne
Checkout our other FileMaker related products and services here:
FileMaker Products and Services