I’m trying to test the Device Authorization Flow for a NodeJS CLI app using the Auth0 example app . I’ve configured a device application in my Auth0 tenant, I’ve launched the CLI sample, and I’ve entered its client ID, my tenant’s domain, the audience for one of my APIs, and selected a scope like of…

Hi @geometric . Thanks for sending the .HAR file. As I suspected, there’s a mismatch of domains used in the flow: The original request (from the CLI) goes to your dev tenant’s domain (e.g. acme-dev.auth0.com) acme-dev.auth0.com shows the login screen. The user action causes the flow to go to Okta …

Device Authorization Flow fails; "Looks like something went wrong!"

Get Help

system Closed October 13, 2021, 6:42pm 6

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.

Topic		Replies	Views
Receiving Unsupported Client for Device Authorization Flow Get Help configuration , application	3	79	October 16, 2024
Auth0 CLI test access token no longer works Get Help apis , application	5	55	February 1, 2025
Example of CLI login through web browser in node Get Help auth0 , api , login	6	8042	April 23, 2021
Auth0 Idp flow doesn't work Get Help sso , application	2	372	April 15, 2025
Auth0 support for the nonce Parameter for Authorisation code flow Get Help sso , application	0	555	February 22, 2024

Device Authorization Flow fails; "Looks like something went wrong!"

Related topics