HGV Journey From Azure B2C to Ory Network
summary
HGV migrates from Azure AD B2C to the Ory Network, replacing a 2,000‑line XML custom policy setup that once required four months to build with a simpler stack: ROPC calls to Azure B2C validate legacy passwords during login, scripts imported identities as verified and map old IDs across databases, and 27 web apps keep cookie authentication while machine‑to‑machine stays on JWT. Migration takes about a month, 3,000 of ~4,000 users already auto‑migrate, monitoring and localized UI land, and a booking expansion adds ~50,000 future identities.
AI-written summary · about
chapters (7)
- 0:00Company overview
- 2:22Challenges with Azure AD
- 4:29Transitioning to Ory
- 6:01Implementing new architecture
- 7:51User data migration strategy
- 9:40Results and future outlook
- 11:43Q&A session
related talks
18mRunning Ory on a 30M users platform
18mShifting Authentication at Scale
49mLesson Learned - General Motors Road to Modern Consumer Identity
01h 04mWho's Who? Federating Identity with Azure B2C
50mManaging Enterprise and Consumer Identity with Azure Active Directory
19mHow TIER IV Replaced Identity Server with Ory
30mTransitioning From Legacy Systems to the Cloud for Better Security
49mGoing Passwordless for Employees: Secure Modern Authentication at Work