Google Oauth2.0 web application's "Authorized redirect URIs" must end with a public top-level domain (such as .com or .org)?

Viewed 18287

When create a Google API Oauth2.0 Credentials on Google Developers Console, I choose "Web Application" Application type.

In the "Authorized redirect URIs" field, I can use http://127.0.0.1/callback, it work fine for me on local development.

but when I want to use Google API Oauth2.0 Credentials on my server(let's say 99.99.99.99), I have to use http://99.99.99.99/callback as my "Authorized redirect URIs", but google give me a warning:

Invalid Redirect: http://99.99.99.99/callback must end with a public top-level domain (such as .com or .org)

Except to bind a public top-level domain to my server, what else can I do?

I develop in Django and use oauth2client to deal with Google API Oauth2 , So there are two table "oauth2_authentication_credential", "oauth2_authentication_flowmodel" in my database which have the credential value in it, I copy them from my localhost to sever, but it doesn't work.

1 Answers
Related