Identity at the Center Identity at the Center #69 - The Role of IAM in an API-First Implementation
Nov 9, 2020
Bill Nelson, co-founder of Identity Fusion and an IAM expert, dives into the fascinating world of API-first implementations. He highlights the importance of designing APIs before applications and contrasts agile with waterfall methodologies for better efficiency. Bill discusses securing APIs through authentication and directories, while showcasing real-world use cases like tractor telemetry. He also shares insights on the future of IAM, emphasizing trends towards passwordless identity and the importance of continuous learning in the field.
AI Snips
Chapters
Transcript
Episode notes
APIs Before Applications
- An API-first approach builds the API before applications so the API drives client behavior.
- This reverses traditional development where APIs were bolted onto finished apps.
Design APIs To Prevent Rework
- Do design APIs first to avoid rework between UIs and back-end services.
- Combine upfront architecture with agile iterations rather than pure agile or pure waterfall.
IAM Is Integral To Securing APIs
- IAM must authenticate and authorize every API client, which may be applications, users, or devices.
- High-performance identity stores like directory services are useful for scalable API traffic.