The benefits of upgrading to FileMaker 16: Security Enhancements

Ben Fletcher • 15 May 2017

Security considerations have always been a priority when building a Custom App, but now we are in the 'cloud-age' it is even more critical to get it right from the outset and to periodically audit. Recent events in the UK such as the NHS ransomware cyber-attack only brings this into sharper focus.

FileMaker 16 has further improved on an already strong set of security features in FileMaker 15 with a number of important enhancements:



HTTP Strict Transport Security (HSTS) optional setting requires that web-client connections use SSL encryption. Although SSL for database connections has long been a part of FileMaker Server this new setting forces web clients (e.g. WebDirect users) to access your FileMaker data over HTTPS connections. Once the web client has completed an HTTPS connection, the web browser prevents the user from downgrading to HTTP connections. This new option is recommended as a simple belt and braces measure.

OAuth 2.0 support for accounts allows you to integrate external authentication providers within your eco system right within the FM platform. This supports Amazon, Microsoft Azure & Google and is controlled by FileMaker Server. If your server has all 3 configured and enabled you will see all 3 icons on your FileMaker Pro login dialog. Single sign on authentication is a popular modern feature that FileMaker have adopted for your convenience.

• Clickable security lock icons. FileMaker Pro has for long indicated the security of your connection to a FileMaker Server via a range of padlock icons. A single click on the padlock icon now provides more details about the security of your connection e.g. certificate details and validity or suggestions for an insecure connection.

Field-level text encryption Is an extra layer of protection for your data. It enhances the already existing comprehensive access restrictions that can be found in the manage security dialog where you can limit access to tables,layouts and fields by privilege set. The new encryption functions can be built into a solution’s logic in order to easily and securely encrypt text or container fields containing sensitive data. Then you can program to either a) allow users access to the decrypted field data when they enter the correct password or b) program your chosen conditions (e.g. specific users) under which to decrypt and display the previously encrypted field data.

There are 3 new extended privileges to lock down access to external interactions with your FileMaker data by privilege set. ‘fmrest’ determines whether members of a privilege set can access the database file from a web service via the new FileMaker Data API available with FileMaker Server. ‘fmurlscript’ determines whether members of a privilege set can run FileMaker scripts from URLs; called using the FMP URL protocol. ‘fmextscriptaccess’ determines whether members of a privilege set can use external applications such as Apple events and ActiveX to control your FileMaker app. If a user’s privilege set does not have the privilege enabled for one of these actions that they perform, they will see the standard FileMaker error; ‘Your access privileges do not allow you to perform this operation’.


Even with the additional security enhancements of the FileMaker 16 platform, it can be an intimidating process to lock down your Custom App if you are new to the FileMaker platform so if you are not sure where to start you can always contact our consulting Team for a security audit.


by Ben Fletcher 30 June 2025
Previously, we have discussed why you may be interested in leveraging local LLMs for to keep data private , how to get started with integrating Claris FileMaker with Ollama and a brief discussion of the trade offs between using the different text generative LLMs (Llama vs DeepSeek). The common thread will all these articles is that these are LLMs optimised for processing text prompt inputs to generate text outputs. However, the Ollama site also provides models that support vision processing , including Gemma3, LlaVA and llama3.2-vision. Impressively, vision processing is still viable using modest Apple Silicon Mac using the llama3.2-vision model. A quick reminder - Why run local AI models on your Mac? Running local LLMs gives you: Full data privacy – your data stays on your machine. No cloud dependency – perfect for secure or offline environments. Faster response times – no network latency. Cost control – no pay-per-query billing. Development feasibility testing - quick prototyping to provide the efficiency of the AI assisted workflow and the fit of different models for your application. Whether you’re in healthcare, legal services, finance, or manufacturing, private AI lets you leverage powerful automation without compromising data compliance or sovereignty. Setting Up llama3.2-vision integration with Claris FileMaker 1. Choose the Right Model The llama3.2-vision build weighs in at 7.8GB and runs with reasonable performance on an entry level M3 class MacBook Air with 24GB RAM. The more advanced 'multimodal' llama4 weighs in at 67GB by comparison - good luck running that with anything less than the 128GB+ RAM configurations of the M2/M3 Ultra or M4 Pro variants. 2. Download and Install Ollama 👉 Download here: https://ollama.com/download Move Ollama.app into your Applications folder Open the app and approve any permissions (including full disk access if prompted). 3. Run Your First Model Open Terminal and run: ollama run llama3.2-vision 4. Check the Server Is Running Open a web browser and go to: http://localhost:11434/ If everything is configured correctly, you should see “Ollama is running” in your web browser page. If not, check your local firewall and security settings to ensure port 11434 is open and accessible. Connecting llama3.2-vision with FileMaker Pro The process for integrating is identical to the text model as a starting point, but the image needs to be converted to Base64 text encoding to send in an additional parameter in the JSON format (" images"; ['imageInBase64'] ). The simplest way to do this within FileMaker is to save your image into a Container field and then convert that using FileMaker's built in Base64Encode() function (this could be stored in a temporary variable or a calculation field as in this example below):
Ai Robot
by Ben Fletcher 17 June 2025
Discover the power of DeepSeek R1—an efficient, open-source AI model ideal for private, local deployment using Ollama and Apple Silicon. Learn how DeepSeek compares to LLaMA, Mistral, and other LLMs in real-world applications, and explore how it integrates seamlessly with Claris FileMaker for secure, on-premise AI automation. Ideal for businesses needing low-cost, high-performance, and fully private AI solutions.
Decorating a blank wall
by Ben Fletcher 30 May 2025
Claris has added dozens of new features with each release of FileMaker - so many that it is hard to quickly see exactly how you might quickly benefit from updating. Here we summarise some of our favourite features we like to highlight to customers looking to upgrade:
A lab working doing research
by Ben Fletcher 22 May 2025
Discover why FileMaker is a cost-effective, flexible LIMS solution for 2025—ideal for labs needing secure, customisable, and rapidly deployable systems.
by Ben Fletcher 16 May 2025
Learn how to run private AI locally using Ollama and integrate it with Claris FileMaker. Discover step-by-step setup, model recommendations, and how to build secure, AI-powered workflows without sending data to the cloud. Perfect for businesses prioritising data privacy and compliance.
Possibility of AI.
by Ben Fletcher 13 May 2025
Integrate Claris FileMaker with local LLMs like LLaMA 3 to boost efficiency with AI—without risking data privacy. Secure, intelligent automation for your business
by Ben Fletcher 29 April 2025
Still running your business on Google Sheets? Spreadsheets are great—until they start holding you back. If you’re managing complex processes, critical data, or multiple users through Google Sheets, it’s time to upgrade.
by Ben Fletcher 25 April 2025
The Claris FileMaker Server 21.1.4 update is now available and includes important fixes that address known issues from previous versions: Key Fixes 1. Field definitions incorrectly read from cache. A bug introduced in version 21.0 caused field definitions to be incorrectly cached, resulting in symptoms such as: Empty related fields Missing value lists and indexes “Insufficient privileges (error -9)” messages 2. Windows only: Server-side script sessions limited by CPU cores. Version 21.1.3 limited simultaneous server-side script sessions to the number of CPU cores on Windows. This impacted I/O-bound environments by unnecessarily queuing sessions. 21.1.4 resolves this by allowing up to 50 concurrent script sessions on Windows before queueing begins—regardless of CPU cores. These sessions may be triggered by schedules, OData, or Perform Script on Server (PSoS). Note: This behavior is not controlled by the AllowPSoS setting. Claris Recommends: To ensure system stability, it is advised to limit active clients to 40 - 45 simultaneous sessions. Exceeding 50 may result in delays, memory overload, or session hangs. Do you need assistance with upgrading? DataTherapy are pleased to announce that Claris FileMaker 2024 (version 21.1) managed private cloud hosting packages are immediately available. DataTherapy can provide scalable, managed FileMaker packages for businesses of all size. Full details of all of our packages can be found here . We can offer a range of a variety of enhanced options such as domain management, custom SSL certificates, VPN, VLAN, disaster recovery and integration with other technologies. If you need additional information on upgrading to the new release, advise on how to migrate your current on-premises FileMaker Server to the cloud, or would like to arrange a free trial of any of our packages then please don’t hesitate to contact our team .
Databases
by Ben Fletcher 16 April 2025
Using Microsoft Excel for workflows and complex data management instead of a dedicated database presents several inherent problems. These issues stem from Excel’s limitations in scalability, data integrity, collaboration, automation, and security. Below is a detailed breakdown of these challenges and how a custom Claris FileMaker App can meet these challenges . . .
Optimising Claris FileMaker App Performance
by Ben Fletcher 25 March 2025
What to do when your FileMaker App isn't running as well as it used to . . .
More posts