Skip to content

CyberFM

  • Home
  • FileMaker Security
  • Disclaimer
  • Privacy Policy
  • Home
  • Wim Decorte
  • Using Active Directory Federation Services (AD FS) to Authenticate Your FileMaker Users
  • Wim Decorte

Using Active Directory Federation Services (AD FS) to Authenticate Your FileMaker Users

Dimitris Kokoutsidis 5 years ago3 months ago4 mins0

Exploring Cross-Platform Authentication with AD FS in FileMaker Server and FileMaker Cloud

Wim Decorte, Apr 8, 2020, Soliant Consulting Blog

Security is in Soliant Consulting’s DNA, which is why our team has been pushing so hard on exploring and documenting various ways you can securely authenticate the users who need access to your FileMaker apps. This is especially crucial if they also need to use the same security identity across other non-FileMaker solutions. So instead of using native FileMaker accounts, what are your options?

We’ve described many of them in a recent blog post and provided a bit of a history of the features in the FileMaker platform over the last dozen versions.

The disparity between the regular version of FileMaker Server and the FileMaker Cloud version is intriguing and needs to be tracked; the authentication requirements that you or your clients may have can force the choice of one over the other.

The most recent 2.1 update to FileMaker Cloud provides the ability to use Active Directory Federation Services (AD FS) to use your on-premise Active Directory for managing your users and the groups to which they belong. We documented the setup here. At the time, it struck us that it was an authentication option only available with FileMaker Cloud, so we set out to do some more exploration. We learned that AD FS can, in fact, be used with the regular version of FileMaker Server as well since it supports the required OpenID Connect OAuth flow.

Steven Blackwell and I added a white paper to our OAuth series to explain why you or your clients may want to use it, and when you do, how to set it up. That white paper is available here.

The authentication landscape currently looks like below. Note that we’ve tested all the Identity Providers (IdP) listed here. The bottom row in the table is there as a reminder that any IdP supporting the proper OAuth flow can most likely be integrated with your FileMaker apps.

Identity ProviderFileMaker ServerFileMaker Cloud (2.x)
On-premise Active DirectoryYesNo
On-premise Open DirectoryYesNo
Local accounts & groups in the OS of the FileMaker Server machineYesNo
Active Directory Federation ServiceYesYes
OktaYes
PingYesNo
OneLoginYesNo
Auth0YesNo
MiniOrangeYesNo
Azure ADYesPartial (works with WebDirect but not FileMaker Go)
AmazonYes (individual accounts only)No
GoogleYes (individual accounts only)No
FileMaker IDNoYes
Any IdP using the Open ID Connect OAuth FlowYesNo

As always, reach out to us here or on the Claris Community Forum with questions or suggestions.

Tagged: Account Active Directory Amazon Authentication Azure Blog Post Cloud FileMaker Cloud FileMaker Go FileMaker Server Google Identity Login OAuth Okta Open Directory Provider Server Test Update UPS Web

Dimitris Kokoutsidis

Post navigation

April 8, 2020
OneLogin for FileMaker User Authentication
April 8, 2020
FileMaker Workflow Security vs. Bad Guy Security

Related Articles

Security – Why It Pays to Keep Up to Date

Dimitris Kokoutsidis11 months ago3 months ago0

FileMaker 2024 Server Q&A with Wim Decorte and Jacob Taylor

Dimitris Kokoutsidis11 months ago3 months ago0