The Nuts and Bolts of API Security: Protecting Your Data at All Times
summary
Claims that API keys are insufficient and that OAuth 2.0 plus OpenID Connect are the practical foundation for real API identity and delegation. Describes the four OAuth actors, the web‑server (authorization code) flow, and token types: access and refresh tokens, bearer vs holder‑of‑key and JWTs as compact by‑value tokens versus opaque by‑reference tokens. Recommends an API gateway that validates tokens at the edge and translates references into by‑value JWTs for internal microservices (at scale: many microservices per day).
AI-written summary · about
chapters (6)
- 0:00Intro
- 0:30What are API keys
- 5:25OAuth 2 Overview
- 13:15JSON Web Tokens
- 14:50OAuth Tokens
- 23:17Microservices
related talks
39mSecure your APIs using OAuth2 and OpenID Connect
20mBuilding a secure API: Overview of techniques and technologies needed to launch a secure API
29mFireside Chat About OAuth 2.0
47mIntroduction to OAuth 2.0 and OpenID Connect
19mIdentity:The missing link in API security
18mAPI Security Simplified: A 5-Pillar Approach
56mSecuring an API Ecosystem with OAuth 2 0
32mSecuring Value in API Ecosystems
