Origin Mismatch error returned from OAuth2 attempt to redirect to the calendar services

9,722 views
Skip to first unread message

RobO

unread,
Nov 1, 2012, 9:54:15 PM11/1/12
to oauth...@googlegroups.com

Problem Summary:
Getting Origin Mismatch error returned from OAuth2 attempt to redirect to the calendar services. The client ID, API Key and all such I have check several times to verify they are identical between the code and the API Console GAE.

Source Code: Attempting to get following example running in my own development environment prior to building my application that needs same services.
http://code.google.com/p/gwt-google-apis/source/browse/trunk/apis/samples/calendar/com/google/api/gwt/samples/calendar/client/CalendarEntryPoint.java?r=2040

Using gwt-oauth2 and gwt

APPLICATION_NAME = "calendarsample"
Client ID:    Client ID is identical in all 3 occurrences:  (1) Source file, (2) App Engine API Console and returned (3) Error "origin_mismatch" Request Details

Redirect URIs:        https://cal2sample.appspot.com/calendarsample/oauthWindow.html

JavaScript origins:    https://cal2sample.appspot.com

API Key:    The API Keys are identical in the source code and API Console

Result: An Error Dialog is presented when attempting to authenticate to calendar in Chrome:

Error: origin_mismatch
Request Details
        scope=https://www.googleapis.com/auth/calendar
        response_type=token
        access_type=online
        redirect_uri=postmessage
        proxy=oauth2relay355812899
        origin=http://cal2sample.appspot.com
        state=305481901
        display=page
        client_id=___________________.apps.googleusercontent.com
        authuser=0

Note that I have not included source code, since it is a google example that has not be modified except for the API key and client id, name.
Desperate and Serious need for answers!
Thank you very much for any ideas.

Vladimir Kolovski

unread,
Nov 1, 2012, 9:56:15 PM11/1/12
to oauth...@googlegroups.com
Hi, 
One of your origins has starts with http, the other with https.

Cheers,
Vlad



--
 
 

Robert Owens

unread,
Nov 2, 2012, 1:42:12 PM11/2/12
to oauth...@googlegroups.com
Thank you Vlad!!

You are correct and that was the issue, the s.
I studied all the characters and missed those essentials at the beginning.  Another humbling moments of great thanks.
Needless to say that if I am going to both authenticating all of the URLs should be https, but I just want to get the basic interface working to start.

Thank you Vlad!


--
 
 

Reply all
Reply to author
Forward
0 new messages