

You can only choose from the groups you set up in your FileMaker Cloud customer console. The AD groups to which the user belongs play no role.

Run your own on-premise server on Linux, macOS, or Windowsīut there are some important differences.

Using AD FS is supported on all FileMaker Servers, whether you: You can host FileMaker Server in the cloud and still use your own in-house AD to authenticate users. That makes AD FS ideal for blended on-prem + cloud strategies. With it, you can use your on-premise Active Directory (AD) without having to make the FileMaker Server machine a member server in that AD domain. Our consultants have written extensively on using various OAuth identity providers and presented on the topic at various DevCons, including at last year’s Engage 2020.Īctive Directory Federation Services (AD FS) is one of these identity providers (IdPs) and a very interesting one. We are big fans of using modern authentication to let users into FileMaker solutions.
