What you’ll learn:
- Common OAuth patterns and use cases
- How to handle OAuth for your users
- OAuth export/import for reduced friction
- Enterprise BYO (Bring Your Own) OAuth apps
OAuth Use Cases
One-Time User Authorization
The most common pattern: each user authorizes once, and you store their OAuth session for future use. How it works:- User clicks “Connect” in your app
- They complete the OAuth flow (e.g., authorize Slack access)
- You store the
oauthSessionIdfor that user - Use that session ID for all future requests
Enterprise BYO (Bring Your Own) OAuth Apps
For enterprise customers who want to use their own OAuth app credentials instead of Metorial’s. Why use BYO:- Use your company’s existing OAuth apps
- Control branding in the OAuth consent screen
- Comply with enterprise security policies
- Manage OAuth credentials in your infrastructure
OAuth Export/Import
For users who want to reduce friction or manage OAuth tokens outside of Metorial sessions.Exporting OAuth Tokens
Export OAuth credentials for use in your own infrastructure:Importing OAuth Tokens
Import existing OAuth tokens into Metorial:- Migrating from another system
- Users already have OAuth tokens from your app
- You want to manage tokens in your own database