invalid_client in google oauth2

Question

I try to make a web page for youtube video upload, therefore I try to get the client id from google api console, and in the api console it shows something like this:

Client ID: 533832195920.apps.googleusercontent.com
Redirect URIs: http://bobyouku.ap01.aws.af.cm/testyoutube.php
https://developers.google.com/oauthplayground

However when I try to test my account using the following URL:

https://accounts.google.com/o/oauth2/auth?client_id=533832195920.apps.googleusercontent.com&redirect_uri=http%3A%2F%2Fbobyouku.ap01.aws.af.cm%2Ftestyoutube.php&scope=https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fyoutube&response_type=code&access_type=offline

It gives out the result of invalid_client. Even when I try it on oauth2 playground, same fail occurs

So anyone knows what's happen?

I found that sometimes the oauth2 client id doesn't work. I don't know why, but when I open a new account and create the client id again, it works. — Bob, Jun 19 '13 at 02:34
Make sure when copy/pasting the client id you don't include a trailing space. That did the trick for me... — andig, Oct 30 '15 at 18:51
for me, i regenerated client secret and use that it worked. Seems the api is still unstable. — Muhammad Talal, Feb 24 '17 at 10:38

score 115 · Answer 1 · edited Oct 07 '14 at 11:05

115

Set/change your product name, I had this issue until I created a product name as same as project name.

The product name can be set in the Consent screen section of the Google Developers Console for your project. Look under APIs & auth in the left navigation and select Consent screen. You need also to set your email address in the box above the product name.

edited Oct 07 '14 at 11:05

SMH_TBZ

103
1
15

answered Oct 23 '13 at 08:03

jojay

1,151
1
7
3

5

Thankyou!! I was getting error ""Error: invalid_client. The OAuth client was not found." Wasted several hours today on this, but updated the product name just now and hey-presto, problem fixed. That error is *so* misleading. – IanB Feb 25 '14 at 10:22
2

What is the product name? – Hubert OG Jun 13 '14 at 14:11
4

It's in the consent screen. You have to fill out the 'PRODUCT NAME' field – Foo L Aug 05 '14 at 23:17
2

This worked. Just to be succinct: set both 'PRODUCT NAME' **AND** 'EMAIL ADDRESS' fields. – b_archer Feb 13 '15 at 23:24
1

That did not work for me. Is it the same name of the app installed and running on the device? I did that. No success!!! – Francisco Souza Feb 20 '17 at 17:26
Not working for me and no info provided to understand what causes the problem – Fabrizio Bertoglio Sep 15 '17 at 10:25
5

Thanks! Saved my day! And I must say, out of all social providers Google has the worse docs and worst UI. It's so overwhelming and confusing along with their bad navigation. I almost always forget how to go to the project configuration page lol. – tintinboss May 18 '18 at 19:30
Such an arbitrary reason – karuhanga Dec 23 '18 at 07:55

Rael Gugelmin Cunha · Answer 2 · 2021-03-23T19:29:33.663

75

After copy values from Google web UI, I had a blank space for:

client_id
secret

And at the BEGINNING and at the END for both.

This happens even when clicking on the "copy" button.

edited Mar 23 '21 at 19:29

answered Jan 19 '16 at 21:39

Rael Gugelmin Cunha

3,327
30
25

2

This issue still persists :P – Abhinay Apr 16 '16 at 14:07
2

Unbelievable, even when clicking the "copy" button in the API console... You'd think Google's developers area would be whitespace sensitive! – Reisclef Dec 05 '16 at 11:00
Unbelievable as well here. Delete those extra spaces on both sides of the string. Then if after following all what has been said here and nothing still works, delete the app/project and re-create it again coz there could be caching issues. – daparic Feb 07 '17 at 19:15
1

Yeap, the issue still exists!!! Holy crap. I omitted one white space and didn't see it until recheck. Thanks. – LukasS Feb 17 '17 at 01:27
1

darn! I saw the space at the end and removed it but did not check for the space in the beginning. – sulabh Jul 27 '17 at 09:30
How come this hasn't been reported? Where the heck I report this stuff?! – Braiam Nov 01 '17 at 01:26
Oh my gosh. Thank you SO much. I could have spent hours confused without realizing that I had an extra newline in my environment variable. – Anvay Mar 06 '22 at 08:49

Shaun Luttin · Answer 3 · 2018-12-23T07:10:31.917

42

Trim the leading and trailing white space from both the client_id and client_secret. Google's copy button does not do this for you.

Set both the email address and product name fields for the OAuth consent screen.

edited Dec 23 '18 at 07:10

answered Jul 12 '16 at 01:02

Shaun Luttin

133,272
81
405
467

3

You probably shouldn't leave your client secret exposed in an answer like that. – Fernando Dec 05 '16 at 16:45
1

@Fernando It's a throw away account. – Shaun Luttin Dec 05 '16 at 22:40
Phew. Had me worried there Shaun :D – Fernando Dec 06 '16 at 20:19
3

How did you get to this screen? – Anthony Kong Feb 23 '17 at 22:19
2

"Throw away account" - not for Google, which tracks you and bundles all accounts you ever used to "associated accounts". And once Google bans one of the accounts - the whole bundle is blocked. Just search for "Google Developer account terminated" on [Reddit](https://www.reddit.com/r/androiddev/). – Alexander Farber Dec 22 '18 at 21:08
Good call @AlexanderFarber... it is better safe than it is sorry especially when the fix is easy. – Shaun Luttin Dec 23 '18 at 07:11
1

@ShaunLuttin You do realize your data is still visible in the answer editing history? Just FYI – Mark Jul 29 '19 at 09:27
Good to know. I appreciate that @Mark. – Shaun Luttin Jul 29 '19 at 16:13

S.Roshanth · Answer 4 · 2014-09-21T17:46:19.910

16

Setting EMAIL ADDRESS and PRODUCT NAME in the consent screen of Google developer console, solves the error "Error: invalid_client. The OAuth client was not found." for me.

edited Sep 21 '14 at 17:46

answered Sep 10 '14 at 09:57

S.Roshanth

1,499
3
25
36

score 9 · Answer 5 · answered Aug 28 '15 at 12:00

9

I had .apps.googleusercontent.com twice in my ID.

It was a copy and paste issue "Your ID HERE".apps.googleusercontent.com

answered Aug 28 '15 at 12:00

Chris Carr

91
1
2

5

Mine was a blank space left on either end :/ – Christian Oct 12 '15 at 16:59

score 8 · Answer 6 · answered Jun 06 '17 at 21:37

8

invalid_client can also simply means that your client ID and client secret are wrong when you create your Oauth2 object.

answered Jun 06 '17 at 21:37

jdcaron

111
2
8

Pedro Romão · Answer 7 · 2016-01-26T16:02:13.130

7

in this thread i found my answer.

I went to google console,
generate a new project, made refresh, because in my case after create the page didn't reload
select new project
create a client ID
use it for what you need

thanks guys :D

edited Jan 26 '16 at 16:02

answered May 27 '14 at 18:33

Pedro Romão

2,285
28
22

Josh Diehl · Answer 8 · 2016-08-31T04:33:02.620

6

In my case this turned out to be something else, namely my code used an environment variable that hadn't been set properly (and stupidly wasnt checked by my code). Setting it, recompiling assets, and restarting the app did the trick.

edited Aug 31 '16 at 04:33

answered Oct 09 '14 at 19:31

Josh Diehl

2,913
2
31
43

1

Same here; I had set it but forgot to restart my terminal – quicklikerabbit Mar 12 '18 at 19:51
Updated my batch file from `set MY_ENV_VAR='a string'` to `set MY_ENV_VAR=a string`, and the error went away. The extraneous quote strings in the environmental variable were being parsed as part of the string itself. – OXiGEN Jan 23 '21 at 10:49

score 6 · Answer 9 · answered Sep 27 '18 at 19:57

6

If you follow the documentation, from this page https://developers.google.com/identity/sign-in/web/sign-in#specify_your_apps_client_id

you'll see

<meta name="google-signin-client_id" content="YOUR_CLIENT_ID.apps.googleusercontent.com">

But it's wrong. It should be

<meta name="google-signin-client_id" content="YOUR_CLIENT_ID">

The issue is that the '.apps.googleusercontent.com' gets added anyway. If you do it like the documentation says, you get '.apps.googleusercontent.com' twice

answered Sep 27 '18 at 19:57

aaronvargas

12,189
3
52
52

Thanks a lot. Changing it as you have suggested did the trick. – Pavan Dittakavi May 15 '20 at 19:38
You are right! It worked as you stated. – Ugur Catak Oct 01 '21 at 07:16

score 4 · Answer 10 · answered Dec 01 '17 at 10:01

4

I solved this by removing unnecessary quotes from my clientID and clientSecret values.

answered Dec 01 '17 at 10:01

OsoGrizz

101
2
13

You sir/maam are a legend! I removed the quotes from my Heroku environment variables. – grabury Feb 07 '18 at 00:12

score 2 · Answer 11 · answered Jul 16 '13 at 23:02

2

Did the error also report that it was missing an application name? I had this issue until I created a project name (e.g. "Project X") in the project settings dialog.

answered Jul 16 '13 at 23:02

random_stackoverflow_user

410
5
7

score 2 · Answer 12 · edited May 23 '17 at 12:10

2

probably old credentials are invalid

see the answer below

stackoverflow answer

or short names may work

see the answer below stackoverflow answer

or product name same as project name as answered already

at times one may include extra space in the

check twice this line so that you are redirected to the correct url

edited May 23 '17 at 12:10

Community

1
1

answered Apr 29 '17 at 06:01

Charles Dominic

345
3
8

score 1 · Answer 13 · answered Dec 27 '17 at 11:00

1

I solved my problem with trim :

'google' => [
    'client_id' =>trim('client_id),
    'client_secret' => trim('client_secret'),
    'redirect' => 'http://localhost:8000/login/google/callback',
],

answered Dec 27 '17 at 11:00

parastoo

2,211
2
21
38

score 1 · Answer 14 · answered Feb 21 '18 at 12:05

1

None of the following were my issue - I resolved this by opening an incognito window. Something was obviously being cached somewhere, no amount of changing auth client settings helped and there were never any trailing or leading spaces in config values.

answered Feb 21 '18 at 12:05

cloakedninjas

4,007
2
31
45

score 0 · Answer 15 · answered Jun 19 '13 at 03:33

0

Check your Project name on Google APIs console. you choose another project you created. I was same error. my mistake was choosing diffirent project.

answered Jun 19 '13 at 03:33

Dio Blando

1

score 0 · Answer 16 · answered Dec 22 '15 at 05:48

At Credentials Accept requests from these HTTP referrers (web sites) (Optional) Use asterisks for wildcards. If you leave this blank, requests will be accepted from any referrer. Be sure to add referrers before using this key in production. Add . (star dot star) . It work fine for me

score 0 · Answer 17 · answered Mar 05 '16 at 13:02

0

I accidentally had a value in the Client Secret part of the URL, but Google Credential does not need a Client Secret for Android OAuth 2 Client IDs. Simply leaving the value blank in the URL did the trick for me.

answered Mar 05 '16 at 13:02

Jason Washo

536
6
22

score 0 · Answer 18 · answered May 12 '17 at 08:41

Steps that worked for me:

Delete credentials that are not working for you
Create new credentials with some NAME
Fill in the same NAME on your OAuth consent screen
Fill in the e-mail address on the OAuth consent screen

The name should be exactly the same.

score 0 · Answer 19 · answered Dec 20 '17 at 11:42

0

Another thing to check:

When you install the GoogleAPIs into a .Net app with NuGet, it will inject a new set of dummy values in your *.config file.

Check that any original values are still in place, and remove dummy entries.

answered Dec 20 '17 at 11:42

Iain Ballard

4,433
34
39

score 0 · Answer 20 · answered Mar 26 '18 at 18:39

0

Deleting client ID and creating new one a couple of times worked for me.

answered Mar 26 '18 at 18:39

Haris ur Rehman

2,593
30
41

score 0 · Answer 21 · answered Jun 14 '18 at 06:07

0

Mine didn't work because I created it from a button from the documentation. I went again to the project and created another OAuthClientID. It worked. Yes, be careful about the extra spaces on right and left too.

answered Jun 14 '18 at 06:07

Hemant Sharma

171
1
6

score 0 · Answer 22 · answered Aug 09 '18 at 08:40

For best results make sure you have the complete details as follows:

{"client_id":"282324738-4labcgdsd4nlh34885s2d34tmi.apps.googleusercontent.com","project_id":"abcd23ss-212808","auth_uri":"https://accounts.google.com/o/oauth2/auth","token_uri":"https://www.googleapis.com/oauth2/v3/token","auth_provider_x509_cert_url":"https://www.googleapis.com/oauth2/v1/certs","client_secret":"23452-dfgdfgcdfgfd","redirect_uris":["http://localhost:6900/auth/google/callback"],"javascript_origins":["http://localhost:6900"]}

This data is always available for download as JSON from https://console.developers.google.com/apis/credentials/oauthclient/

score 0 · Answer 23 · answered May 25 '20 at 23:51

If you are in Meteor JS, you have to use clientId instead appId:

Since facebook uses appId and google clientId.

ServiceConfiguration.configurations.upsert({
    service: "google"
}, {
    $set: {
        clientId: process.env.OAUTH_GOOGLE_APP_ID,
        loginStyle: "popup",
        secret: process.env.OAUTH_GOOGLE_SECRET
    }
});

I spent some hours to realize over that.

score 0 · Answer 24 · answered May 28 '20 at 03:41

I wish I had seen this post before, because there are a lot of things I had to find out trial and error. A lot can go wrong with this. Here's another issue I had:

Whe you specify the Authorised Javascript origins or Authorised redirect URIs, make sure to include your domain with and without www. So https://google.com and https://www.google.com

Also I had uploaded an Application logo. Because of that, the consent screen required a review... which takes forever. Don't upload an Application logo, or be very patient.

score 0 · Answer 25 · answered Oct 08 '21 at 10:20

0

this could also be because of not using https url.

In other words,this only works with https. It works with http only in localhost

answered Oct 08 '21 at 10:20

Muhammad Ali

341
2
7

score 0 · Answer 26 · answered Feb 23 '23 at 21:56

0

The solution that worked for me was to remove the ' single quotes and remove additional spaces at the end of the client id and secret in the .env file

answered Feb 23 '23 at 21:56

German

192
1
11

invalid_client in google oauth2

26 Answers26

Linked