Google: Permission denied to generate login hint f

问题:

I am trying to create a Google sign-in and getting the error:

Permission denied to generate login hint for target domain

Before you mark this a duplicate, this is not the same as the question asked at Google sign in website Error : Permission denied to generate login hint for target domain because in that case the questioner was on localhost, whereas I am getting this error on the server.

Specifically, I have included the url of the server in the Authorized Javascript Origins, as in the following image:

and when I get the error, the request shows that the same url was sent, as in the following image:

Is there something else I should be putting in my Restrictions page? Is there any way to figure out what is going on here? Is there a log at the developer console that can tell me what is happening?

回答1:

Okay, I figured this out. I was using an IP address (as in "http://175.132.64.120") for the redirect uri, as this was a test site on the live server, and Google only accepts actual urls (as in "http://mycompany.com" or "http://localhost") as redirect uris.

Which, you know, THEY COULD HAVE SAID SOMEWHERE IN THE DOCUMENTATION, but whatever.

回答2:

I know this is an old question, but it's the first result when you look for the problem via Google, so I'll share my solution with you guys.

When deploying Google OAuth service in a private network, namely some IP that can't be accessed via the Internet, you should use a magic DNS service, like xip.io that will give you an URL that your browser will resolve to your internal IP. You see, Google needs to be able to reach your authorized origin via your browser, that's why setting localhost works if you're serving it on your computer, but it won't work when you're deploying outside the Internet, as in a VPN, intranet, or with a tunnel.

So, the steps:

1. get your IP address, the one you're deploying at and it's not a public domain, let's say it's 10.0.0.1 as an example.
2. add http://10.0.0.1.xip.io to your Authorized Javascript Origins on the Google Developer Console.
3. open your site by visiting http://10.0.0.1.xip.io
4. clear your cache for the site, if necessary.
5. Log in with Google, and voilà.

I got to this solution using this answer in another question.

回答3:

If you testing in your machine (locally). then dont use the IP address (i.e. http://127.0.0.1:8888) in the Client ID configuration , but use the local host instead and it should work

Example: http://localhost:8888

回答4:

If you are using http://127.0.0.1/projects/testplateform, change it into http://localhost/projects/testplateform, it iwll work.

回答5:

Just ran across this same issue on an external test server, without a DNS entry yet. If you have permission on your local machine just edit your /etc/hosts file:

175.132.64.120  www.jimboweb.com

And use use http://www.jimboweb.com as an authorized domain.

回答6:

To allow ip address to be used as valid javascript origin, first add an entry in your /etc/hosts file

10.0.0.1 mydevserver.com

and then add this domain mydeveserver.com in Authorized Javascript Origins. If you are using some nonstandard port, then specify it with your domain in Authorized Javascript Origins.

Note: Remove your cache and it will work.