question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[Feature Request] Support OAuth2 Device code authorisation flow

See original GitHub issue

I would like httpyac to support the OAuth 2.0 Device authorization grant for the openid variable replacer.

Ref. RFC8628 Example of usage: Microsoft Identity platform

Proposal for httpyac:

GET https://graph.microsoft.com/v1.0/me
Authorization: openid device_code msidp

Reason:

This is a great way of authenticating using applications where you cannot/don’t want to modify the redirect Url, and don’t have access to/don’t want to leak the client secret. And contrary to the implicit and hybrid authorization flows, the device code flow hasn’t been deprecated by the OAuth standard and best practices.

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Reactions:1
  • Comments:13 (13 by maintainers)

github_iconTop GitHub Comments

1reaction
fredrikhrcommented, Nov 7, 2021

@AnWeber I think this looks great! I tested it with Microsoft Identity platform and it works like a charm! As expected it keeps the session and even picks up the refresh_token if you specify the offline_access scope.

I also managed to recompile the VS Code extension with the new code and tested the UI features of the flow. Everything checks out fine! 👍

1reaction
fredrikhrcommented, Nov 4, 2021

Can you add another button to copy the user_code to the clipboard?

Read more comments on GitHub >

github_iconTop Results From Across the Web

OAuth 2.0 device code flow - Microsoft Entra
A long string used to verify the session between the client and the authorization server. The client uses this parameter to request the...
Read more >
Device Authorization Flow - Auth0
The Device Authorization Flow contains two different paths; one occurs on the device requesting authorization and the other occurs in a browser. The...
Read more >
OAuth Device Flow | Curity Identity Server
The OAuth 2.0 Device Authorization Grant (aka Device Flow) is an extension to the original OAuth 2.0 spec. It solves the problem of...
Read more >
OAuth 2.0 Device Flow - ForgeRock Backstage
Perform the following steps to request a user code in the OAuth 2.0 device flow: The client creates a POST request to the...
Read more >
OAuth 2.0 Device Authorization Grant - keycloak-community
Keycloak must provide a new endpoint for the verification process of the user code which is returned by device authorization request.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found