When software is provided as a managed service (SaaS), using a multi-tenant approach helps minimise costs for the deployments and operations of each tenant. In order to leverage these advantages, applications need to be designed so that they can be deployed to support multiple tenants, while maintaining isolation for security reasons. At the same time, common deployment and operation models are required so that new SaaS versions can be deployed to existing tenants, or to onboard new tenants, in a reliable and efficient way.
That blog post is about the usage of the "Quarkus Security OpenID Connect Multi Tenancy" implementation in an own small example, how to extract a tenant and reconfigure OIDC configuration for Keycloak.
How to simply organize workspaces and the debugging configuration separated from source code saved in GitHub and how to simply configure attach debug for Quarkus in Visual Studio Code
Authentication and Authorization for Java Microservices with Keycloak, Quarkus and Microprofile.