Technical Tip: Origin Mismatch Error using Google Authentication
Description
This article describes the behavior when a user is attempting to authenticate in the Captive Portal using Google Authentication, and the following error appears:
Origin_Mismatch
An origin mismatch error is presented by Google when the authentication API request is coming from a different URL than what was authorized in the Google Developer Console application dashboard.
The security level and domain name in the URL must match exactly.
Example: If https://guardian.mycompany.com is an authorized origin, but the request came from either https://guardian/ or http://guardian.mycompany.com in the user's browser, the mismatch error will occur.
To confirm URL's listed as Authorized Origins:
Example: If https://guardian.mycompany.com is an authorized origin, but the request came from either https://guardian/ or http://guardian.mycompany.com in the user's browser, the mismatch error will occur.
To confirm URL's listed as Authorized Origins:
The below instruction are current as of 11/22/2015. See the below link:
https://developers.google.com/console/help/new/ for more information).
- Log into https://console.developers.google.com using the Google account used for appliance integration.
- Select the project name
- In Project Details view, Select APIs & Auth.
- Under APIs & Auth, Select Credentials.
Under Authorized Javascript Origins, confirm the URL's listed and compare to the URL in the client browser when trying to authenticate.
Solution
Add the missing URL to Authorized Javascript Origins. Multiple URL's can be added.