User: A user is, yup, a user - you or me logging into a FileMaker database. Group: We'll be setting up groups which are to be used in the same way as we know them in FileMaker - we may have a user group and an admin group that end up with a different set of privileges granted to them by FileMaker as determined by you the developer. Client Scopes: A client scope is a grouping of information about a user that is passed back to FileMaker Server, and we'll be needing the user's email address and what groups they belong to. Client: As FileMaker developers we think of a client as a user connecting to FileMaker Server with either Pro or Go, but in the Keycloak world think of this as an application that will use Keycloak for authentication - for us that's FileMaker Server of course. Realm: You can consider this to be your organization or company, but in a more complex deployment it could be a department. The ones we'll be touching on in this article are: Each IAM system has their own wording for various parts of the system. To begin, let's explain the elements that we'll be setting up. If you're interested in some of the background information and details, please read those white papers. We strongly encourage all FileMaker developers to read their white papers, a list of which can be found here. We will be focusing on the steps to get Keycloak and FileMaker Server working. Before We Beginīefore we jump into Keycloak, a reminder that the inspiration behind this series was the result of the work of Wim Decorte and Steven Blackwell. We'll be using the Keycloak Administrator Console to do this, so let's get logged in and get things set up. So far in our Keycloak series we have been setting up the infrastructure for our server to run on, but now that's done we can actually configure Keycloak to act as our authentication server for FileMaker. 
Lesson in Brief: Setting Up A Realm, Client, Groups And Users
0 kommentar(er)
