JS adventures in Azureland
summary
Wraps Azure AD around an existing React username/password flow by using the state parameter as a per-login key so the backend stores the returned ID token by that state and the frontend posts the state to a /state-auth endpoint which exchanges the stored ID token for the app JWT preserving the original auth flow and logout hygiene. Also pulls minute-level GetBlob transaction metrics with the Azure Monitor SDK authenticated by a service principal and persists filtered time series JSON into Azure Table Storage via the v2 storage SDK with token expiry and rate-limiting precautions, working end to end.
AI-written summary · about
chapters (28)
- 0:00Introduction
- 4:45Demo
- 22:00Storage
- 26:15GetBlop
- 26:51Constraints
- 28:28Diagnostics
- 29:01Documentation
- 29:12Platform Metrics
- 29:27SDKs
- 30:08Monitor
- 30:21NPM
- 32:26Service Principle
- 33:10Subscriptions
- 34:44List
- 35:32Package
- 36:03Properties
- 36:13Optional params
- 36:51Filter query
- 37:28JSON formatted
- 37:43Time series array
- 38:30Empty objects
- 38:58Real metrics
- 39:44No API
- 40:13SDK
- 40:39Table objects
- 41:11Table service
- 41:55Table storage
- 42:57Suggestions
related talks
01h 02mMastering Secure Login Mechanisms for React Apps
54mWho's your user? OpenID from the ground-up
09mBeyond the Login Page: Authentication in Next.js
14mLeverage Hybrid Apps for Secure Auth
11mHow I created my brand using Static Web Apps with Blazor and Azure Functions
41mAin’t no party like a localhost party
33mAuth for React.js APP
08mAdd login to your React App in no time