Learn to Navigate the Perils and Pitfalls of Multi-Tenant Identity...
summary
Multi-tenant IAM grows from a simple login UI into dozens of hard requirements: OAuth2 (75 pages) and OIDC (44 pages) differences, per-tenant password hashing choices (bcrypt vs Argon2 vs PBKDF2) and divergent audit and certification needs. Real examples: a webshop serving consumers, partners and workforce; healthcare tenants demanding different hashing and session lifetimes; federation quirks with Entra ID. Compare shared system vs dedicated system tradeoffs (noisy neighbor, compliance, cost) and prefer established frameworks and regular pen tests and certifications rather than bespoke auth plumbing.
AI-written summary · about
chapters (9)
- 0:00Multi-tenant identity challenges
- 1:03Simple login hides complexity
- 4:18Identity complexity multiplies
- 6:09Multi-tenant identity needs
- 9:43Authentication and tenancy questions
- 11:10Regulatory and security per tenant
- 15:15Shared vs dedicated systems
- 19:34Choosing architecture
- 20:37Summary and best practices
related talks
01h 12mIdentity 2.0: the what, why and how of social and federated login
35mIdentity and Access Management for the Decade Ahead
08mModern Identity Management and Learning from Developers Around the World
32mModern And Secure IAM For Modern Applications
12mOptimizing Multi-Tenant SaaS
37mCustomer Identity for Modern Apps and APIs
22m4 identity factors you didn't know you needed to support in your SaaS.
01h 02mWhy IAM is the new perimeter, and how to govern it