Identity providers, your app, and everything in-between
summary
Shows how a Flask app registers with Microsoft Azure, redirects users to Microsoft’s login, exchanges the returned code for id, access, and refresh tokens via the OAuth2 Authorization Code (auth code) flow, decodes the JWT id_token for profile claims, and calls Microsoft Graph to read OneDrive files using the access token. Covers token refresh using offline_access, and the on-behalf-of (OBO) flow for separated front-end/back-end (two client apps), uses MSAL and worked in a Nokia production app.
AI-written summary · about
chapters (11)
- 0:00Introduction and speaker background
- 2:16Identity provider scenarios explained
- 4:45OAuth 2.0 and OpenID Connect overview
- 5:28OAuth 2.0 code flow deep dive
- 7:57Flask app configuration with Azure
- 10:26Callback endpoint and token exchange
- 11:53JWT token structure and decoding
- 13:39Accessing user resources with tokens
- 14:42Refreshing expired tokens
- 15:23On-behalf-of flow for separated services
- 18:09Python libraries and resources
related talks
59mDemystifying OAuth, JWTs and Azure AD
39mSecuring your apps with OAuth2 and OpenID Connect
39mSecure Mobile Apps with the Microsoft Identity Platform
54mWho's your user? OpenID from the ground-up
58mLet's talk Auth
23mAndroid Application with Microsoft Identity Platform
12mIntegrating Microsoft Identit(ies) into your applications
41mEasy-Auth: The Easiest Way to Secure Your Application in Azure App Service