Pass On Access: User to User Data Sharing With OAuth
summary
Demonstrates sharing a bike‑lock IoT (Skylock) account by turning OAuth’s user→app tokens into user→user delegation using OpenID Connect’s userinfo endpoint, issuing a second access token that names both the authenticating client and the resource owner. Compares two implementations: a central access table (DB lookups per microservice, high coupling) versus delegated tokens (JWT or reference tokens minted by the OIDC server, microservices only validate tokens). Shows a working prototype pattern and tradeoffs for token management and microservice scaling.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 0:56Skylock
- 3:35Use Case
- 4:13Sharing
- 4:30Delegation
- 7:00Access Tables
- 9:38Microservices
- 10:30Delegate Access
- 11:00OpenID Connect
- 12:05User Info
- 14:40Access Token
- 15:45OAuth Flow
- 16:44Micro Services
- 17:56Regular Access
- 18:58Delegated Tokens
- 19:16Conclusion
related talks
31mOAuth 2.1 And OpenID Connect
47mIntroduction to OAuth 2.0 and OpenID Connect
28mOAuth 2.0 and OIDC
19mOAuth and OpenID Connect for Microservices
33mOAuth and OpenID Connect Deep Dive
54mWho's your user? OpenID from the ground-up
39mSecure your APIs using OAuth2 and OpenID Connect
01h 00mImplementing OpenID Connect and OAuth 2.0 – Tips from the Trenches
