Using Auth0 in your applications means that you will be "outsourcing" the authentication process to a centralized login page in the same way that Gmail, YouTube, and any other Google property redirects to accounts.google.com whenever a user signs in.
With input-constrained devices, however, rather than immediately authenticating the user, the device asks the user to go to a link on their computer or smartphone to authenticate. This avoids a poor user experience for devices that do not have an easy way to enter text. If you’ve ever signed in to your Netflix account on a device like a Roku, you’ve already encountered this workflow.
Your user will authenticate on their computer or smartphone, and Auth0 will generate an Access Token that will be passed back to your device application. The Access Token can then be used to call your API.
This flow can be used with native applications only.
When your app needs to fetch user data from your API:
For devices, Auth0 uses the Device Authorization Flow.
To implement the Device Authorization Flow, you can follow our tutorial: Call Your API Using the Device Authorization Flow.
Step-by-step instructions for tasks
API endpoints, libraries, and best practices
Understand the fundamentals
Was this article helpful?
Any suggestion or typo?Edit on GitHub