ISO FileMaker Magazine

If there's one thing you shouldn't ignore from the start of any FileMaker solution, it's the way security is going to factor into your creation. You need to know who the users and groups are and what their access rights are. These access rights are called privilege sets within FileMaker.

All too often, security may be an afterthought because most of the fun typically lies in creating solutions to the problems. The real trick is to create the solution to the problem while simultaneously considering how security wraps around that problem.

Unfortunately, with FileMaker being such a flexible platform, testing those access rights is not obviously easy. We have one simple way of testing one privilege set versus another: logging out of the system and then logging back in as another user. This process, while critical, can seem like a hassle, so it's often deferred. With the information in the associated video and technique file, you'll enjoy learning about a very easy-to-use system that allows for testing things quite easily. The solution simply takes advantage of part of how FileMaker works after the authentication process. Need to up your security game within FileMaker? You're sure to find some answers within this solution.

Security. While it isn't as sexy as a nice UI widget or as crafty as a really cool scripted workflow, setting up your security is something you must consider before any database deployment. When it comes to security, you can't miss a beat. If you do, then that one attack vector might be the one that bites you. And, unless your FileMaker solution is never going to connect with the network at large, knowing who can do what within your system is an essential requirement of security.

Getting to know FileMaker's privilege sets, and how they work, is one thing. But, weaving this knowledge into a system which provides a good degree of flexibility is another. If you're interested in the User/Group/World permissions model, then applying it to your FileMaker solution isn't too hard. You just need know which fields to add and how to make them interact with the rest of the security model in order to accomplish your intended goal.

This video, and the companion file that comes with it, will provide you with the best starting point possible for figuring out how you might want to integrate your security objectives. If you've never quite gotten FileMaker's security under your belt, then give this video and file a good look over.

Managing user accounts within FileMaker is pretty easy and straight forward. This, however, is an aspect of access control which only applies to what a user can do within the world of FileMaker's interface.

When it comes to your own solution's user interface, it doesn't exist until you create it. And, of course, FileMaker knows nothing about what you create. It's just a tool. This means it's up to you to add your own security controls.

In order to do this, you need to take advantage of all of FileMaker's security controls. Once you understand how to use these controls, you can create an access system which has various levels of access and allows some users to advance or reduce the access of other users. If you have a database which needs to have managers, employees and various levels of access then you need to watch this video.

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.

Crafting a complex security setup within FileMaker can be a bit daunting. Possibly, because of how you interact with and establish security within FileMaker. Despite what may seem obvious, it isn't just about what FileMaker's default security provides, but how you integrate the controls which you have access too. When solution security setup and testing is the after thought, there's a lot of potential for accidental holes in the security model. However, if you take the upfront steps of setting things up from the beginning, the whole problem is a much easier nut to crack.

This video and the companion technique file will walk you through the process of establishing your security model. It offers some useful tips and tricks for working with FileMaker's cumbersome security dialogs and helps you test your security in a much more fluid way.

If you've felt like your solution was lacking in security and you knew there was more to take advantage of, then you'll certainly learn a few more things in this video. If you've never even worried about setting up security on your FileMaker solution then make sure to watch this video!