-
Notifications
You must be signed in to change notification settings - Fork 20
Add remembered device flow recipe #170
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
pages/recipes/api-sms-remembered-device/magic-link-authenticate.tsx
Dismissed
Show dismissed
Hide dismissed
| {user.trusted_metadata?.known_devices && user.trusted_metadata.known_devices.length > 0 && ( | ||
| <div style={styles.knownCountriesContainer}> | ||
| <p style={styles.successNote}> | ||
| 💻 <strong>Known Devices:</strong> {user.trusted_metadata.known_devices.join(', ')} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.



Add a recipe for a remembered device flow using DFP.
Rather than try and make some of the existing components/api endpoints extensible (take dynamic redirect URLs, dynamic cookie names, etc.) I just created dedicated components and endpoints for this flow.
It's more (boilerplate) code, but IMO dedicated components/endpoints/etc that are obviously for this recipe make it clearer to follow, and in the context of a recipe book the goal is clarity and not code reuse/optimization.
Companion guide incoming.

