OAuth Device Flow Beta 404 on code generation? #24377
-
I’ve filed a support ticket for this as well, but curious if anyone has had success implementing the new Device Flow auth (as described in https://docs.github.com/en/developers/apps/authorizing-oauth-apps#device-flow)? I’m always getting a 404 on the POST to the device/user code generator (Step 1 in the docs). I’ve tried it with both existing and new GitHub and OAuth apps that have been opted-in to the Device Flow beta- I assume I’m missing something dumb and obvious here. In addition to multiple apps in multiple orgs, I’ve tried different scopes (and no scope at all), messing with the
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Just closing the loop here for @nitzmahone’s OP. As mentioned, there was an internal support ticket created, and the solution was provided: If you want to provide your Just in case anyone happens to come across the same, in their searches! |
Beta Was this translation helpful? Give feedback.
Just closing the loop here for @nitzmahone’s OP.
As mentioned, there was an internal support ticket created, and the solution was provided:
If you want to provide your
client_id
as JSON, you’ll need to set theContent-Type
header toapplication/json
. Alternatively, you can send this as form data or query parameters with no extra headers.Just in case anyone happens to come across the same, in their searches!