I am what IAM - the testing challenges of digital transformation
summary
Company runs identity service for 12 million emails with 99.9% uptime (goal 99.999%), supports >10 auth flows, and drops brittle Selenium UI checks in favor of API‑first design, tenant-per-customer infrastructure as code, continuous delivery and feature‑toggle driven configurability. Tests split into vertical endpoint checks and horizontal use‑case flows; CI runs Dockerized Postman collections. Remaining problems: flaky UI skins, social‑login account linking, protocol misuse by integrators and DDoS/bot threats — many fixes work but edge cases still bite.
AI-written summary · about
chapters (11)
- 0:00IAM challenges introduction
- 4:00Login automation with Selenium
- 7:40Identity platform redesign
- 13:01Business versus technical guidelines
- 14:44Rethinking test automation strategies
- 17:23Vertical and horizontal API testing
- 20:04API naming conventions challenges
- 23:55UI automation in configurable systems
- 26:24Testing IAM gateway corner cases
- 29:41Social registration and service desk gaps
- 31:53Q&A
related talks
35mIdentity and Access Management for the Decade Ahead
31mIAM and why it is important in Cloud environments
31mEnterprise Identity Management on Rails
01h 02mWhy IAM is the new perimeter, and how to govern it
24mThe Great Balancing Act: Security, UX, and Identity
50mTraffic safety: Auditing and enforcing IAM best practices
40mModern Identity Management
50mOperationalizing Identity: IAM for Customer Service