Google API authentication: Not valid origin for the client

B

18

91

When making an auth request to the Google API (gapi), it's returning false on the checkOrigin.

I have removed any client id's or anything that would link directly to my account and replaced it with a regex indicating what the data is for reference.

Url: https://accounts.google.com/o/oauth2/iframerpc?action=checkOrigin&origin=https%3A%2F%2Flocal.tools&client_id=(\d{21})

My origin url is a local url, which is https://local.tools

Result: {valid: false}

I'm using the example found here without deviation (except for replacing clientid with my 21 digit clientid): https://ga-dev-tools.appspot.com/embed-api/third-party-visualizations/

The items I'm trying to display show up nicely on the demo site, but aren't getting past the Not valid origin for the client error on my local.tools site.

Bedeck answered 2/3, 2017 at 21:26 Comment(3)

and "local.tools" is deffo configured in the API console and your local server is running on port 80? Try editing your /etc/hosts to point your demo site URL to 127.0.0.1 and see what happens. – Eucalyptus 6/3, 2017 at 22:37

Nothing good would happen because my development environment is not on 127.0.0.1. It also doesn't matter what port it's running on. It can be used on other ports besides port 80. – Bedeck 20/3, 2017 at 14:57

Google API authentication: Not valid origin for the client. --- It might be in case, while you are using same email id for creating client id and for sign-in through webpage – Sommer 9/10, 2020 at 10:58

L

80

I received the same console error message when working with this example: https://developers.google.com/analytics/devguides/reporting/embed/v1/getting-started

The documentation says not to overlook two critical steps ("As you go through the instructions, it's important that you not overlook these two critical steps: Enable the Analytics API [&] Set the correct origins"), but does not clearly state WHERE to set the correct origins.

Since the client ID I had was not working, I created a new project and a new client ID. The new project may not have been necessary, but I'm retaining (and using) it.

Here's what worked:

Create a new project
Add and Enable the Analytics API
Create a new credential - ensure that it is an OAUTH credential (scroll to the bottom of this page for instructions https://developers.google.com/api-client-library/javascript/start/start-js#Setup).

During creation of the credentials, you will see a section called "Restrictions Enter JavaScript origins, redirect URIs, or both". This is where you can enter your origins.

Save and copy your client ID (and secret).

My script worked after I created the new OAUTH credential, assigned the origin, and used the newly generated client ID following this process.

Lorelle answered 6/3, 2017 at 19:25 Comment(11)

Yes, that was what I needed. Thank you! Seems like it should be obvious now, but the docs are a bit hard to follow. – Bedeck 9/3, 2017 at 17:58

if I test with a localhost, how can I add the oauth there? for example If I need to let access to localhost:9000/en/login – Doubledealing 15/3, 2017 at 9:19

You don't need to worry about the oAuth callback. When you use the example given, there is a little button that says something along the lines of "google Authenticate" or I don't remember. But it's there and you click on it and a popup window comes up to authenticate. Adding my domain to the origins is what I needed to do, including after uploading the example to the server. I had to add the server URL to the origin domains. – Bedeck 20/3, 2017 at 14:55

My script worked with new credential in the old app. I believe this is a bug from Google, because I did try adding my origin to my old credential. – Biography 4/7, 2017 at 21:53

Had the same issue and these steps worked for me! The trick was Enabling the Analytics API before creating the Credentials – Clevis 3/8, 2017 at 3:27

In my case it was the type OAuth needed to fix – Hull 28/5, 2018 at 14:3

Year after year I keep findig myself back at this answer. Nothing works --> Delete app --> Create new app with the domain added to whitelist --> It works. I mean, I get it, "have you tried turning it off and on again" is a meme for a reason. But it's incredibly frustrating that Google just refuses to improve these services, and there is no way to contact an actual helpful support-person instead of a generic chatbot. Oh well. See you here in 2021 I guess. – Compote 25/2, 2020 at 14:56

Make sure you add the URIs when creating the credentials not after. – Anemology 7/7, 2020 at 12:1

It seams 2021 is worse : setup that was working before does not work now. It seams you cannot enter "localhost" origin anymore. It says "not valid origin" – Vauntcourier 8/2, 2021 at 9:37

Original article behind the link: web.archive.org/web/20170301044410/https://… You can find the credential page here: console.cloud.google.com/apis/credentials edit the entry to define your JS source URLs (origins). – Isaac 11/8, 2021 at 13:0

Activate Analytics API here: console.cloud.google.com/apis/library/… – Quirites 22/11, 2022 at 10:48

C

183

Clear your browser cache. Started getting this error in Chrome and then I created a new client id and was still getting the issue. Opened firefox and it worked, so I cleared the cache on Chrome and it started working.

Cahra answered 25/1, 2018 at 2:33 Comment(9)

Cannot believe cache plays that much role in it. – Messina 6/8, 2018 at 23:40

I had issue like this in iOS safari. The origin was accepted in chrome on iOS but not updated in safari. I’m hoping it will time out sooner or later. – Myocardiograph 10/12, 2018 at 6:3

Or go take a break for an hour or so. Especially if on a device where you don’t want to clear all cache or on mobile where it’s harder to do so. – Myocardiograph 10/12, 2018 at 7:59

Amazingly enough, clearing the browser cache actually solved this issue for me as well... – Nodus 11/12, 2018 at 13:41

Perfect! It works for me after clearing the cache, Thanks a lot. – Burden 5/1, 2019 at 10:35

I had this problem too. If you go to the settings on the dev tools in chrome, there is an option to disable the cache when the dev tool is open. – Drumm 24/1, 2020 at 20:19

Love it when the solution to all my problems is clearing the cache :) – Haeckel 11/4, 2020 at 11:16

Gotta love it when you question your code and sanity, but all you needed to do is clear the cache. THANK YOU! – Pindling 15/6, 2020 at 21:52

Just a tip in case you don't want to lose all your cookies, history, etc. In chrome you can enter as a different user - so just enter as guest, so you wont have to delete all your browsing history. – Underdrawers 8/7, 2021 at 12:16

L

80

I received the same console error message when working with this example: https://developers.google.com/analytics/devguides/reporting/embed/v1/getting-started

The documentation says not to overlook two critical steps ("As you go through the instructions, it's important that you not overlook these two critical steps: Enable the Analytics API [&] Set the correct origins"), but does not clearly state WHERE to set the correct origins.

Since the client ID I had was not working, I created a new project and a new client ID. The new project may not have been necessary, but I'm retaining (and using) it.

Here's what worked:

Create a new project
Add and Enable the Analytics API
Create a new credential - ensure that it is an OAUTH credential (scroll to the bottom of this page for instructions https://developers.google.com/api-client-library/javascript/start/start-js#Setup).