How TIER IV Replaced Identity Server with Ory
summary
TIER IV replaces a Python homegrown identity server with Ory Kratos, Hydra and Oathkeeper, finishing the migration in three months. A custom UI/proxy called Poseidon handles login/consent flows and ID mapping; legacy numeric IDs remain alongside new Kratos UUIDs to avoid breaking microservices. Passwords require on‑the‑fly reformatting because initial import needed direct DB updates; team converts Django’s PBKDF2 password hashes into Kratos’ expected format during migration.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:07Existing environment
- 3:20Choosing Ory stack
- 6:08Architecture changes
- 9:24Use case flows
- 11:51Replacement implementation
- 15:08Data migration
- 17:37Conclusion
related talks
23mRe-Engineering: Ory Kratos and Ory Keto in production
25mImplementing the Ory stack at Padis
16mHow to move your RBAC into Ory 
25mAnaconda Unified authentication with Ory 
24mBuilding a community management infrastructure with Ory open source software
19mDavids Slingshot: Leveraging Ory
15mKeynote: Future Directions for the New ID Stack
22mCustomizing Ory Keto with global-scale data sharing requirements