This is what the non-working credential looks like. Sets the options of this finder with the values stored in a given string. 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. Know that you will have to use this URL for your request as well event though it translates to Solution 2 Reseting Chrome cached solved it for me. Had that error myself at some point and this fixed it. The only difference is that with the 'addHerokuAfter' credential, I added the authorized origin in after creating it. Google API authentication: Not valid origin for the client Loaded 0 When making an auth request to the Google API (gapi), it's returning false on the checkOrigin. Solution 1 If it's all the same to you, try adding to your authorized JavaScript origins instead. Per the screenshots below: my 'addHerokuAfter' credential did not work, but the 'whitelistfrombeginning' credential did. But if I simply stumbled into buggy behavior, then perhaps validation here would be helpful so I could report the bug to google's cloud platform. Should it have worked? If not, I'd like to know why. Now I don't understand why adding an authorized origin to an existing credential didn't work. I had no luck after going into my google API developer console to add the relevant domain under Authorized JavaScript origins to my existing credential.Īfter browsing around SO, I resorted to trying like the answer suggested to just create a new credential from scratch that includes the domains under authorized javascript origins upon creation. However, Is there an advantage in allowing any origin over disabling CORS There must be one, otherwise this option is nonsense. Idpiframe_initialization_failed', details: 'Not a valid origin for theĬlient: 'MY DOMAIN' whitelist this origin for your project's client ID I found two possible solutions: a) Disable CORS b) Set Access-Control-Allow-Origin to I didn't have the chance to try these solutions yet. I initially encountered the following error when i tried to set up an 'authorize/login' button on an html page. So I did, I created a new credential for the same project and used my new user-id and it worked perfectly.

Is there an advantage in allowing any origin over disabling CORS? There must be one, otherwise this option is nonsense.My question is a follow up to an answer to a related but different question. I read on several places on the web people use to redo the creation of the credentials to get it to work.

I didn't have the chance to try these solutions yet. Please go to and register this origin for your project’s client ID. To fetch the resource with CORS disabled. Not a valid origin for the client: has not been registered for client ID. Opaque response serves your needs, set the request's mode to 'no-cors' When I try to avtorizirovatsya originals I wrote For the first time, you have to be online or Authorization temporarily not available. Have the server send the header with a valid value, or, if an Origin 'null' is therefore not allowedĪccess. We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time.

'Access-Control-Allow-Origin' header has a value 'null' that is notĮqual to the supplied origin. Since the last update, Chrome blocks this request with the following message: Access-Control-Allow-Origin in the response header is null too, because the origin of the resource is something like file://., which is changed to null. When I run the app on Android, origin in the header of a network request is null.

Quotnot a valid origin for the client