Once they are closed, click the Configuration menu item and under the Server Information section, click Stop Database Server.
So, next, and this is important, in the FileMaker Server admin console, click the Databases menu item and close all databases. Next, on that same page, scroll down as needed and under the Database Sign In section, enable External Server Accounts and then enable the Microsoft entry. In the three fields, add some text - it doesn't matter what as we'll be adjusting this later - and then hit Save Authentication Settings. Under the Identity Authentication Settings section, click Change for the Microsoft entry - it must be the Microsoft one as this is the only one that supports groups. Open the FileMaker Server admin console, click on the Administration menu item along the top and then External Authentication in the menu on the left. Edit the entry for Microsoft Azure AD in a XML file to include details of our Keycloak serverĬompared to what we've done up to now, this should be a walk in the park.Configure and turn on the Microsoft Azure AD external authentication setting.As far as FileMaker Server is concerned, the outline plan is: Note that we are using FileMaker 19 in this example, although this technique does work with some other versions - check those white papers for details. If you want more detail on how and why we're taking the steps below, again check out the white papers by Wim Decorte and Steven Blackwell, a list of which can be found here. Some of the information below is still relevant but check out our more recent post on the Custom IdP configuration here. A Custom Identity Provider option is available in the FileMaker Server Admin Consle in 19.4, making the process of setting it up far easier. While we still encourage you to read this article in your Keycloak journey, with the release of FileMaker Server 19.4, editing the xml as detailed below is no longer required.
#FILEMAKER SERVER 11 TUTORIAL UPDATE#
We're almost there, let's get stuck in! Update : In the final stretch of our epic Keycloak journey, we turn our attention to FileMaker and the items we need to take care of there to bring this all together. In our last article we configured Keycloak with a realm, client, users and more, ready for it to act as our authentication server for our FileMaker database. Lesson in Brief: Adjusting External Authentication And Setting Up Groups
0 kommentar(er)
