The official documentation is in the FileMaker Knowledge Base. Most of the setup is done in ADFS, which you will then follow up by configuring the ADFS service in your FileMaker Cloud subscription to make the two connect. Make sure that each user has their email set since that property will be used to identify the user as set up in the FileMaker Cloud subscription. And two users: Jane Manager, who belongs to both groups, and Joe Staff, who only belongs to the FM_staff group. Note: because ADFS requires the Windows IIS web server and access on port 443, it is not a good idea to install the ADFS role on a machine running FileMaker Server.įor this example, the AD domain is named soliantdev.cloud, and we have two groups: FM_managers and FM_staff. For this walkthrough, you must already have a working on-premise Active Directory and have ADFS installed. This is different than the on-premise regular version of FileMaker Server, which can work with both on-premise AD and Azure AD.ĪDFS is a component you install on Windows Server, a role that you add to the server. FileMaker Cloud 2.1 does not currently work with Azure AD. To be clear, ADFS is not Azure AD (Microsoft’s Active Directory in the cloud) rather, ADFS allows you to use your on-premise Active Directory. Using Active Directory Federation Services (ADFS)īesides Okta, you can also use Active Directory accounts through Active Directory Federation Services (ADFS). In my blog post from February 24, you will find a walkthrough of how to set up Okta as the Identity Provider (IdP) for client authentication in FileMaker. When Claris launched Cloud 2.1, its “FileMaker Server in the Cloud” product introduced the capability to let users sign in with accounts other than their FileMaker ID, specifically using either Okta or ADFS authentication.
0 kommentar(er)
