Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

There's no "Other" for "Application type" when creating OAuth Client ID #383

Open
Kyle-Law opened this issue Nov 6, 2020 · 2 comments
Open

Comments

@Kyle-Law
Copy link

Kyle-Law commented Nov 6, 2020

No description provided.

@backwardm
Copy link

@Kyle-Law I just ran into this myself and saw an answer on Stack Overflow that it's now called "Desktop app" in the Application type drop down.

I followed the same steps using "Desktop app" instead of "Other" and it worked when creating a valid OAuth 2.0 Client ID. My use-case was for a command line app which triggered the 'go to this URL, allow and then paste in the token' steps in the CLI.

@jtoy
Copy link

jtoy commented Sep 2, 2022

I just tried with desktop app and doesn't work for me, I get:

Error 400: invalid_request

You can't sign in to this app because it doesn't comply with Google's OAuth 2.0 policy for keeping apps secure.

You can let the app developer know that this app doesn't comply with one or more Google validation rules.

If you’re the app developer, make sure that these request details comply with Google policies.
redirect_uri: urn:ietf:wg:oauth:2.0:oob

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

No branches or pull requests

3 participants