Repository navigation
Scalable Multi-Tenant SSO with Common IDPs (Microsoft, Google) — Architectural Guidance Needed #40045
Unanswered
the-corner-guy
asked this question in
Q&A
Scalable Multi-Tenant SSO with Common IDPs (Microsoft, Google) — Architectural Guidance Needed
#40045
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Overview
We're building a multi-tenant SaaS platform and need to support authentication via common enterprise IDPs like Microsoft Azure AD and Google. The goal is to allow customers to use their existing identities without requiring per-tenant app registration or approvals.
Current Architecture & Limitation
Each tenant maps to a separate Keycloak realm. This causes scalability issues, particularly with Azure AD:
Azure AD apps have a 256 redirect URI limit.
Each realm requires a unique redirect URI.
Keycloak does not support:
What We Need
A scalable solution where:
What We’ve Tried
Request
Looking for architectural guidance on:
This is a common SaaS use case—any guidance or direction would be greatly appreciated.
All reactions