![]() ![]() Well, that transition is complete and the first release of the new underlying technology is now fully supported and available as Keycloak 17. For a couple of years now, the Keycloak team have been working on transitioning away from WildFly to something called Quarkus, using the project name Keycloak.X. Keycloak 16 and previous versions were built upon an underlying technology called WildFly. We will be referring back to previous articles for certain steps and procedures, so if this is new to you, do read the introductory article of our previous series to get familar with what’s what. Please read their series of white papers here to learn about various external authentication options for FileMaker. Our forays into Keycloak can entirely be attributed to their work in this area and we are indebted to them. So, let’s get to it! IntroductionĪs we have before, we need to acknowledge the excellent work from Wim Decorte and Steven Blackwell who have and continue to push the subject of security in the FileMaker platform. We have previously written a complete and lengthy series about Keycloak, an Identity and Access Management solution that can be used with FileMaker to provide centralized management of users, multi-factor authentication, password-less authentication, act as a broker for other Identity Providers and more.īut the folks over at Keycloak HQ have been relentless in their pursuit of improvements to the software, and in mid February 2022, Keycloak 17 was released with a new underlying technology that requires us to revisit and update our deployment tutorial.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |