Skip to content

Fix token url for device code flow#220

Merged
ramosbugs merged 2 commits intoramosbugs:mainfrom
randomairborne:patch-1
Jun 15, 2023
Merged

Fix token url for device code flow#220
ramosbugs merged 2 commits intoramosbugs:mainfrom
randomairborne:patch-1

Conversation

@randomairborne
Copy link
Copy Markdown
Contributor

@randomairborne randomairborne commented Jun 15, 2023

this should fix #219, as according to https://learn.microsoft.com/en-us/azure/active-directory/develop/v2-oauth2-device-code that was the wrong token url

@LorenzoLeonardo
Copy link
Copy Markdown
Contributor

That sample is just for common use, you can change that common to tenant id if you are using it with for tenant.

@ramosbugs
Copy link
Copy Markdown
Owner

ramosbugs commented Jun 15, 2023

@LorenzoLeonardo seems like the order of common/v2.0/oauth2 vs. common/oauth2/v2.0 within the URL may have been an issue?

@randomairborne
Copy link
Copy Markdown
Contributor Author

randomairborne commented Jun 15, 2023

@ramosbugs that was in fact the issue, it was causing a 404 which was being reported in an opaque way.

@ramosbugs
Copy link
Copy Markdown
Owner

@LorenzoLeonardo I'm going to merge this unless you have objections

@ramosbugs ramosbugs merged commit 49d8798 into ramosbugs:main Jun 15, 2023
@ramosbugs
Copy link
Copy Markdown
Owner

Thanks for fixing!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

microsoft_devicecode flow broken

3 participants