Google OAuth2 Authorizing OAuth token error: redirect_uri_mismatch

Question

I am Creating and Authorizing an OAuth Token according to this webpage: https://code.google.com/p/google-mail-oauth2-tools/wiki/OAuth2DotPyRunThrough

But I got this error: redirect_uri_mismatch.

The redirect URI in the request: urn:ietf:wg:oauth:2.0:oob did not match a registered redirect URI
from_login=1
cookie_policy_enforce=false
scope=https://mail.google.com/
response_type=code
access_type=online
redirect_uri=urn:ietf:wg:oauth:2.0:oob
as=-80019291b2cb8ed
display=page
pli=1
client_id=......
authuser=0
hl=en

I thought this might be helpful: Google OAuth 2 authorization - Error: redirect_uri_mismatch

But when I try to register the redirect url to my console, I was told that the url is invalid.

score 50 · Accepted Answer · answered Jul 31 '13 at 16:45

50

The redirect_uri (urn:ietf:wg:oauth:2.0:oob) is only applicable to those Google client ids that have been generated for installed applications. You can go to your console and create a new client id of this type.

answered Jul 31 '13 at 16:45

oravecz

1,146
11
16

Yes, you are right. I solved this by creating the client id for **installed applications**. – Cacheing Jul 31 '13 at 17:20
6

DOH. Using one created for web application. I want the last 4 hours of my life back! – Mike Devenney Jul 16 '14 at 18:28
3

I can not find option for creating OAuth2 Key for Installed Applications. – Satyam Singh Aug 17 '18 at 07:32
@SatyamSingh You've probably figured this out by now, but they don't call it `Installed Applications` anymore. You just select iOS or Android or other. – Symphony0084 Mar 22 '20 at 10:29

score 32 · Answer 2 · answered Sep 24 '13 at 19:23

32

Just in case if you're using Google+ javascript button (with web application), you have to put postmessage instead of actual URI. It takes me almost whole day to figure out this, because Google docs doesn't clearly stand it for some reason.

answered Sep 24 '13 at 19:23

Mike Keskinov

11,614
6
59
87

1

This saved me hours of digging around, I thank you. There is so much conflicting / legacy documentation out there! – Drewid Mar 26 '14 at 11:03
Ditto - I just wasted GOBS of time trying to figure this out! – Rob Jul 15 '14 at 01:07
1

I am new to oauth. I couldnt understand this "postmessage" you suggested. how does it work instead of a url. – Sagi_Avinash_Varma Nov 04 '14 at 16:09
"after the dialog is shown" that's what "postmessage" refers to. This advice saved me! Google+ Platform sign in (with offline access) was driving me NUTS in Node.js! – Jmlevick Apr 27 '15 at 20:44
@Drewid How do I send a POST message instead of an URI? – Honinbo Shusaku Jun 16 '15 at 16:52

score 10 · Answer 3 · answered Oct 19 '14 at 07:04

10

For my web application i corrected my mistake by writing

instead of : http://localhost:11472/authorize/
type :      http://localhost/authorize/

answered Oct 19 '14 at 07:04

Guven Sezgin Kurt

1,199
11
13

So we can have localhost as URI and it will work for published web sites? For live/published web sites, how come a localhost works? Am I missing something here? – Unbreakable Dec 22 '16 at 05:42
This is the only solution that actually worked for me. If you are just poking around with the Quick Start then this is what you need to do!!!!! – zypherman Sep 19 '17 at 16:19

score 7 · Answer 4 · answered Aug 21 '13 at 13:54

7

When you register your app at https://code.google.com/apis/console and make a Client ID, you get a chance to specify one or more redirect URIs. The value of the redirect_uri parameter on your auth URI has to match one of them exactly.

answered Aug 21 '13 at 13:54

Kathir

1,212
15
25

score 7 · Answer 5 · answered Mar 30 '15 at 01:06

7

Please note that the 'redirect_uri' value of the Token request need to be the same as the 'redirect_uri' value of the Authorization request.

answered Mar 30 '15 at 01:06

Fadelovesky

121
2
3

exactly, thanks! my problem was that to receive authorization code I used `urn:ietf:wg:oauth:2.0:oob:auto` (*auto*!) but for authorization I didn't know exactly the same uri should be used – Andriy Tylychko Jun 28 '15 at 19:32

score 5 · Answer 6 · answered Oct 14 '15 at 08:01

5

Lost 4 or 5 hours with this... use 'postmessage' as parameter value, not the real Redirect Uri...

$client->setRedirectUri('postmessage');

answered Oct 14 '15 at 08:01

DevFdbck

51
1
2

i am java guy, but changing redirect uri to postmessage worked for me. two hours spent on this ****. – OGM2 Apr 01 '20 at 11:10

score 3 · Answer 7 · answered Nov 12 '13 at 22:08

For anybody that is still stumped with this problem, you must have the 'Platform' set to 'Native (Windows Mobile, Blackberry, desktop, devices, and more)' when registering your app in the Google Cloud Console, otherwise, it will not let you use 'urn:ietf:wg:oauth:2.0:oob' as the redirect URI.

score 3 · Answer 8 · answered Feb 19 '16 at 16:21

3

In my case, instead of creating web app, i just chose Other in: OAuth Client ID > Other

and thats it.

answered Feb 19 '16 at 16:21

Goran Jakovljevic

2,714
1
31
27

score 1 · Answer 9 · edited May 23 '17 at 12:03

1

2015July15 - working signin started causing Error 400 with Error: redirect_uri_mismatch

i posted a solution on a similar SO QUESTION: changed loading script to

<script src="https://apis.google.com/js/client:platform.js?onload=startApp></script>

edited May 23 '17 at 12:03

Community

1
1

answered Jul 15 '15 at 16:46

tony gil

9,424
6
76
100

score 0 · Answer 10 · answered Dec 19 '19 at 00:55

For my native app, I tried dozens of different things. I finally got it to work by using "redirect_uri=http%3A%2F%2Flocalhost%3A1234" where 1234 is the port number. This has to be identical in the two requests (authorization code and the access token). Notice the use of percent encoding.

score 0 · Answer 11 · answered Nov 04 '20 at 07:24

0

I was getting this error, because I was incorrectly following the steps for installed application flow here

https://github.com/googleads/googleads-python-lib/wiki

instead of the server to server flow.

answered Nov 04 '20 at 07:24

M3RS

6,720
6
37
47

score 0 · Answer 12 · edited Jan 13 '21 at 06:38

0

The easiest way is to create the service account.

Create the document using your own account and share it with the service account.

edited Jan 13 '21 at 06:38

Dharman

30,962
25
85
135

answered Jan 13 '21 at 06:32

zawhtut

8,335
5
52
76

score 0 · Answer 13 · answered Jan 31 '23 at 04:47

redirect_uri must be an EXACT MATCH on the developers console.

In my case, this was due to a trailing slash( / ).

In the Google Cloud console, I had http://localhost:8080 under the redirect URIs in the list while my code was sending http://localhost:8080/ while making the oAuth call.

Google OAuth2 Authorizing OAuth token error: redirect_uri_mismatch

13 Answers13

Linked