Anaconda Unified authentication with Ory
summary
Anaconda abandons an in‑house IAM for Ory Cloud and reports a staged migration that preserves internal tokens so existing services need no code changes, swaps gateway validation to accept Ory tokens, and uses PyScript as the integration testbed. Enterprise customers gain attached email domains to organizations and a login flow that replaces passwords with SSO buttons per org. Migration notifies users with migrated accounts with one‑month opt‑out, covers a 35M user ecosystem, and finishes mostly smoothly with only a few account fixes.
AI-written summary · about
chapters (9)
- 0:00Introduction to unified auth
- 4:13Anaconda ecosystem needs
- 7:27Initial in-house IAM solution
- 10:01Why choose Ory
- 13:14Migration to Ory process
- 16:51Post-migration architecture
- 17:11Enterprise SSO features
- 20:51Next steps and future plans
- 22:19Closing and Q&A
related talks
18mRunning Ory on a 30M users platform
18mShifting Authentication at Scale
19mHow TIER IV Replaced Identity Server with Ory
19mDavids Slingshot: Leveraging Ory
23mRe-Engineering: Ory Kratos and Ory Keto in production
25m Introducing the Ory Network
15mKeynote: Future Directions for the New ID Stack
23mBuilding a Google-like IAM system from scratch through Ory products