HTTPS Required
Overview:
Starting Wednesday, October 23rd, 2019 DayBack will start enforcing secure connections using https and for some users, further action may be required.
Who's Affected:
DayBack Online accounts that use FileMaker Server as a data source where the php relay file is on a server that doesn't support https and currently load DayBack using "http://app.dayback.com" rather than "https://app.dayback.com"
Details:
Starting Wednesday, October 23rd, 2019 DayBack will start enforcing secure connections using https. This means that any attempts to connect to http://app.dayback.com will automatically be redirected to https://app.dayback.com.
We’re constantly evaluating the security of our products and requiring the use of http in DayBack helps make sure that we’re meeting internet security standards. When the connection from DayBack to your FileMaker server is also established over http, this ensures your data is fully encrypted, making it much harder for anyone to get a hold of that data.
Although it would be best if the FileMaker Server was using SSL, it is not necessary to use DayBack. As long as the php relay file can be accessed over https there will not be any issues with an https connection to app.dayback.com.
If you are unsure what the php relay file is please check out our documentation on setting up FileMaker server in DayBack: https://docs.dayback.com/article/126-integration
Actions Required:
Step 1 - Enabling a valid HTTPS connection to the PHP relay file:
A valid public domain name is necessary for any SSL certificate. If you don’t currently have a domain name you can easily purchase one from providers like NameCheap or Hover. There are even free domain options like freenom but we wouldn’t recommend those for a production environment.
Option 1: Cloudflare flexible SSL connection
For the fastest and simplest method, if security is not your main concern, you can set up a flexible SSL connection using the free pricing plan of the Cloudflare service. This will allow for a secure HTTPS connection from the browser to the Cloudflare CDN, but from there to your PHP relay file will still be insecure if you don’t have a valid SSL certificate on your server.
You will need to create a free account at https://www.cloudflare.com. Then transfer your domain DNS to Cloudflare so your domain points properly to the Cloudflare service. Once your domain is properly using Cloudflare for your DNS you can select the “Flexible” SSL certificate option.
Setting up Cloudflare for your DNS provider can be seen here:
https://support.cloudflare.com/hc/en-us/articles/360019093151-
Then activate flexible SSL as outlined here:
https://community.cloudflare.com/t/ssl-tls-app-settings/53186
Be aware that if you don’t have an SSL certificate on your server the traffic will only be encrypted from the client (browser) to the Cloudflare CDN. From the CDN to your server will not be encrypted. To ensure the traffic is encrypted from your server all the way to your client you would need to install an SSL certificate on your server. If an SSL certificate is installed on your server you could choose the “Strict” SSL option on Cloudflare, or choose to not use that service at all and connect directly to your server using HTTPS.
Option 2: Install an SSL certificate on your server
If you would like to set up an SSL certificate on your server, FileMaker has a support document on this subject. Since the PHP relay file is most likely hosted in the web server directory you may need to follow the directions for the multi-machine server environment to ensure both the web server and the FileMaker server are properly set up even if both services are on the same physical server:
https://www.filemaker.com/learning/custom-app-academy/204/setting-up-filemaker-server-with-ssl.html
Option 3: Have us do it for you
If you’d like help getting an SSL certificate installed on your FileMaker server please reach out and we'll set up a screen-share to go over your requirements.
Step 2 - Updating your DayBack calendar sources to use https:
In DayBack's FileMaker Server source settings, change the following options in each one of your sources:
Server address: [Your new server domain name if changed]
Server protocol: https
Server port: 443