Receiving Unsupported Client for Device Authorization Flow

Hi, I am using the Device Authorization Flow feature and following this guide to set it up Call Your API Using the Device Authorization Flow. I have two Auth0 tenants, one for local testing and another for a live environment. When I set up my Client for my local testing tenant everything works as expected and I am able to authenticate using Device Authorization. However, when I followed the exact same steps for my live environment’s Auth0 Tenant I am now seeing Failed Device Activation and Failed Exchange with the descriptions as “Access Denied: Unsupported client ” when I try to authenticate. I have looked through additional requirements and limitations here Call Your API Using the Device Authorization Flow and everything seems to be identical within both tenants. I have not been able to find any similar problems online so I was hoping to find some further guidance here.

Additional context: I have an API that uses Auth0 to authenticate requests. Currently it is only being hit by a React frontend but I want to extend my API to also support a CLI. I thought that Device Authorization Flow would be a good fit here since I can initiate the flow from the CLI and reuse a common login flow that my frontend client would experience.

(Also I wasn’t sure what tags would be most relevant here, please let me know if I should change these)

Also to clarify, I am able to form the Device Authorization’s Verification URI and clicking it brings me to the login page I expect, it’s just after logging in on that page in my live environment I receive this error and I see the Failed Device Activation + Failed Exchange logs from the Monitoring section in the Management Dashboard

:man_facepalming: I did more digging and it turns out this was an error thrown from my post-login action, oops

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