In addition to the more typical external authentication methods, FileMaker supports client authentication using OAuth accounts from Google, Amazon, and Microsoft. In this instance, I needed to set up a FileMaker Cloud server to use a company’s directory accounts, which were hosted at Azure. In order to set this up I hit a couple of minor complications, which I’m going to cover here.
I needed to set up some monitoring for FileMaker Server that made moderately heavy use of the XML interface for Custom Web Publishing (CWP). The server was mostly working well, but was due for a rebuild, or at the least, an upgrade, but the client wanted to squeeze out one more season before we did this.
Continue reading “Monitoring FileMaker’s CWP Connectivity”
In looking back at our initial approach to logging FileMaker PSoS (Perform Script on Server) activity, I reflect back on a number of times where this has been extremely helpful. If you have come to rely on the benefits of PSoS then you also know some of its challenges — one of the biggest is debugging and monitoring how long sessions take.
Since FileMaker 16 introduced JSON, in new systems we’ve switched over to using JSON as the main way of exchanging data for parameters. Because we also use PSoS in new systems, we updated our method for PSoS Logging and this blog entry talks about the changes we made there and also restates the usefulness of this log.
Continue reading “Logging PSoS Activity: Episode III – Return of the JSON”
FileMaker 16 has been out for several months, however we wanted to call attention to a change that can effect your application’s use of server side scripting. Recently, we upgraded a client project to FileMaker Server 16, and found that critical functionality had mysteriously broken. After a bit of sleuthing and gnashing of teeth, we found that changes to the output of
Get(SystemDrive), when executed server-side (PSOS or via a scheduled script), was the culprit.
Apple’s macOS Server 5.x has a rather different Apache configuration compared to the core macOS setup or those used in previous versions of Server. In particular, an instance of Apache is used as a proxy to any ‘backend’ copies of Apache. Here’s how to work around this…
If you are FileMaker developer, but new to the notion of web APIs and web development in general, then you might take on a kind of deer-in-the-headlights look when confronted with FileMaker Server 16’s new Data API, aka “REST API”. Fear Not! It really is simpler and more straightforward than you might expect. I like to take the attitude that no skill is difficult, only unfamiliar. With study and repetitive exposure and practice, any skill can be mastered.
Since FileMaker Server version 13, FMS has used its own Apache configuration files on macOS instead of just adding includes to the OS configuration files. Because of this, the technique I mentioned here no longer works for newer systems. This new arrangement has reduced issues for FileMaker Server’s web connectivity.
If you’ve installed the FileMaker Pro client using a “For Teams” license, or as part of your FileMaker Cloud server usage, you may see a new dialog in FileMaker Pro.
In version 15, FileMaker has introduced a a new user-based licensing model. With FileMaker for Teams and FileMaker Cloud, a license allows use of Server and Client software based on the number of subscribed users.
Optimized for FileMaker 15, the new version of bBox includes 160 examples
We are pleased to release another update to bBox, v0.84 of our free utility plug-in to extend FileMaker solutions to other programs, code libraries, and OS X functions including Python, Ruby, AppleScript, Perl, Bash/sh, XPath, and SQLite.