Demystifying User Management for Voice Apps
summary
Explains how to link Amazon and Google Assistant users to an existing database using OAuth/OpenID Connect and a hosted identity provider (Octa), showing a deployed C#/.NET API on Azure and optional AWS Lambda. Uses the authorization code flow with refresh token enabled, returns OpenID claims (name, email, custom favorite_band) inside the access token, and maps the platform’s randomized user ID to the local user record. Demoed a music skill that successfully reads a stored favorite band; author reports ~40 skills built and enterprises with 50k–100k users.
AI-written summary · about
chapters (25)
- 0:00Introduction
- 0:25Agenda
- 1:28User Authentication
- 6:08Account Linking
- 11:12Alexa Skills Kit API
- 11:39Setting up User Management
- 18:54User Management Blog Post
- 27:11Alexa Developer Portal
- 31:26Webhooks
- 32:39Invocation
- 33:31Language
- 35:16Testing
- 36:31Distribution
- 37:26Enable Skill
- 40:11Testing the Skill
- 41:26Reopening the Skill
- 41:41Asking Questions
- 42:21Count Linking
- 42:51Implicit Grant
- 45:11Access token expiration
- 45:31How to disable a skill
- 46:21How to login
- 46:46What is my favorite band
- 47:11How does Heather know that
- 47:41Custom information
related talks
47mWho's your user? OpenID from the ground-up
20mIdentity providers, your app, and everything in-between
39mSecuring your apps with OAuth2 and OpenID Connect
20mPass On Access: User to User Data Sharing With OAuth
20mOAuth 2: A closer look
01h 02mDemystifying Web API Security in Azure
26mAzure Managed Identities: Why are you still using anything else?!?
32mDiscussing Customer Identity with Mindvalley and Auth0