ISO FileMaker Magazine

Using multiple files for developing a robust FileMaker solution can be pretty normal when you plan out the distribution of your data and servers. Some solutions benefit from breaking out part of the solution into one or more separate files.

So, whether taking the load off a given server or simply planning for quicker data access across multiple time zones, one of the bigger problems which pops up with your standard FileMaker accounts is password management. This is where it becomes much easier to use external authentication.

In earlier days, we only had access to Active/Open Directory or system accounts hosted on the same machine as FileMaker server. But, since FileMaker Server 16, we now have the ability to use external authentication through Oauth. This means we can use a third party like Amazon, Google or Microsoft in order to allow users to access solutions and manage their own passwords.

If you're looking for an easier way to manage the users of your solution, then you'll find out how it works and how to make it happen within this video about Oauth External Authentication.

FileMaker 16 added a variety of new features designed to support its new ability to interact with web services using JSON. One of those supporting features was the addition of more cryptographic functionality.

Previously, the only native feature available was an MD5 hash. At the time of it being added, it was already out of fashion as a security based feature, but it could be used to compare two things against each other.

By adding new encryption and decryption capabilities, we are now able to encrypt and decrypt data directly within the database itself. This means we can, if desired (and your security policies allow it), store things like credit cards and other sensitive information. While the functions themselves are pretty straight-forward, it’s always nice to know the ins-and-outs of how to implement a feature properly.

There's nothing more heart wrenching than when you first realize that something horribly wrong has just happened. It's such a distinct feeling that we all know what I'm talking about.

Just imagine being at the airport and you've got your laptop bag just beside you. After going through security, you feel like you're ready to have a relaxing flight. As you turn to grab your bag, you suddenly realize it's gone! Jumping up, you scan around and see absolutely no evidence of anything having happened. Nothing.

I can't even type those words without having the feeling come over me. The same thing applies to a server administrator when they realize their server has been breached. Yet, it's our job to do our best to learn what we can about protecting our data.

Well, this video has a lot of the critical information you need to know about protecting your FileMaker files. No matter where you are in the learning curve about building a FileMaker system, the information in this video is must know type of knowledge.

The security of your FileMaker data should always be a top priority. If you don’t know how to implement FileMaker’s Privilege Sets, then you need to learn as quickly as possible.

While the dialogs for security can seem a bit obscure and difficult, it only takes a few trips in and out to get a feel for how you can lock things down.

In this video, I showcase a simple system I created which covers topics such as Granting full access to scripts and why, locking off security related fields, using Global fields and local fields for temporary access escalation and other security related items dealing with privilege sets.