Simeï Steiner

Integrating OpenID Connect (OIDC) with a single Identity Provider is standard practice in ASP.NET Core. But what happens when your architecture requires multi-tenancy where every tenant has their own isolated Keycloak Realm? Standard middleware configurations often fall short when dealing with dynamic issuers and multiple signing keys. This session guides you through the complexities of handling multiple Keycloak realms within a single ASP.NET Core application. We will look at the limitations of the default authentication handlers and implement a robust solution to dynamically validate tokens from different realms. You will leave with a clear strategy for securing multi-tenant applications without compromising on tenant isolation or code maintainability.