Externalizing IAM with Keycloak

The very first thing to externalize is in a modern information system IAM. Except for extremely rare cases, nobody should ever implement their own authentication mechanism as the security stakes are so high and the entry barriers are way too high for most organizations. When a simple password was enough, almost any application had its own authentication mechanism, sometimes with clear-text passwords in the database. That time is now over, and the smallest company needs at least a multi-factor authentication, which necessitates the ability to send SMS, for example, for the confirmation of authentication. This is of course way out of reach for small companies such as DemoEditor, and even large companies prefer to turn to security specialists for their needs.

In addition, since DemoEditor, like a lot of small and medium-sized enterprises, has an Office 365 offer that comes with user management via Azure AD, it would be a waste not to use it for its internal...