Google web client OAuth 2.0 JavaScript origins with private IP or local DNS name

301 Views Asked by At

I am trying to set up a Login with Google button for a web app of a company intranet.

Is it ok to use a login with Google button for a web app that is not published on the internet but is only for an intranet?

Specifically, it possible to set a local domain name or a private IP as authorized origins for Javascript?

I just found this similar question but without answers...

Following this question suggestions, I also already tried:

  • nip.io and sslip.io.

  • using a mycustomdomain.com and put in Windows hosts file "127.0.0.1 mycustomdomain.com"

  • attach the :80 port to every Javascript Origins

In all these cases I keep receiving a client-side error "The given origin is not allowed for the given client ID" despite, for the last two cases I have these allowed javascript origins, this request header and this in the Windows host file:

10.9.1.112 rd.raicam.com

Where 10.9.1.112 is just a test server with the webapp loaded to it... just for not use localhost and try to make the login work.

I would be grateful if you could provide me with a suggestion... I haven't found any official Google clarification on this topic.

0

There are 0 best solutions below