We identified Keycloak as an authentication and authorization framework. It comes with a login page that can be customized with themes. However, the login page and user workflow are opinionated by Keycloak. The theming has limitations for user interface design and user workflows. If we use our own login page and integrate Keycloak we make it probably hard to leverage from the full set of features Keycloak provides.
This research task here should give us a good understanding what are the consequences of using our own login design and workflows vs. theming the Keycloak user interface. The goal is to have enough information to make a well-informed decision. We have the following questions identified:
- What are the consequences when we follow Keycloak upgrades for both variants?
- What are the limits of features when we decide to write the workflow and UI ourselves?
- What are the limits of user interface design if we theme the opinionated Keycloak UI?
- What are the limits for each variation in the scenarios self-hosting vs. hosted as a customer service