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.
Support / Documentation for limited device authorisation flow
See original GitHub issueAccording to this page “OAuth 2.0 for TV and Limited-Input Device Applications” is generally supported in the google apis. However, I couldn’t find any hint about it in the google-api-dotnet-client.
Maybe the AuthorizationCodeFlow can be used for this, but I couldn’t find any example.
Finally I managed to implement a draft version of this authorisation workflow for youtube. In case this would be an enhancement for the google-api-dotnet-client, I’m willing to contribute it and make it more robust. However, I would need some support to understand how and where to integrate into the existing code base.
Issue Analytics
- State:
- Created 6 years ago
- Comments:9 (1 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
This an #1812 are the same, and we are tracking both on the backlog. Removing this one from the backlog as duplicate in #2223
OK, as I wrote I did not get it. I thought after glancing at the documentation that limited device auth was the way of authorizing by “external” browser. Thanks for the quick answers.