OBiTALK Community

Region Specific Technical / Service Provider Support => North America - Including Google Voice, Skype, etc. => Topic started by: videobruce on September 01, 2016, 04:37:58 AM

Title: Redirect message when trying to configure GV
Post by: videobruce on September 01, 2016, 04:37:58 AM
When I either try to login here via Google Voice or specifically configure this OBi202 to GV I keep on getting this error popup:

Quote"400. That's an error.
Error: redirect_uri_mismatch
Application: Google Voiceâ„¢
You can email the developer of this application at: admin@obitalk.com

The redirect URI in the request, https://services.obitalk.com/obinet/pg/obhdev/gvtoken, does not match the ones authorized for the OAuth client. Visit https://console.developers.google.com/apis/credentials/oauthclient/565436231175-v2ed4f21arki7dt43pks0jlsujatiq2i.apps.googleusercontent.com?project=565436231175 to update the authorized redirect URIs.

Request Details
access_type=offline
approval_prompt=force
scope=https://www.googleapis.com/auth/googletalk https://www.googleapis.com/auth/userinfo.email https://www.googleapis.com/auth/userinfo.profile
response_type=code
redirect_uri=https://services.obitalk.com/obinet/pg/obhdev/gvtoken
client_id=565436231175-v2ed4f21arki7dt43pks0jlsujatiq2i.apps.googleuserconten"

Clicking on the 'learn' link takes you to a page with this;
QuoteSet a redirect URI
The redirect URI that you set in the API Console determines where Google sends responses to your authentication requests.

What on earth is all of this about? (yes, I did use that email address, but never received a reply)
Title: Re: Redirect message when trying to configure GV
Post by: videobruce on September 01, 2016, 05:05:00 AM
I tried two browsers and I get the same thing. Then I went to Google's 'Cloud Platform' and I get a "failed to load".  This is ridiculous.
Title: Re: Redirect message when trying to configure GV
Post by: LTN1 on September 01, 2016, 05:56:47 AM
Quote from: videobruce on September 01, 2016, 05:05:00 AM
I tried two browsers and I get the same thing. Then I went to Google's 'Cloud Platform' and I get a "failed to load".  This is ridiculous.

I get the same problem and while it is an annoyance, I am able to log in by going to the main www.obitalk.com site to sign in.
Title: Re: Redirect message when trying to configure GV
Post by: videobruce on September 01, 2016, 06:22:33 AM
That doesn't solve the problem of registering with GV.

But, since I know know that there is a $60 plan with PhonePower, this ridiculous hassle isn't worth it.  I did a search and the 1st hits are that "stackoverflow" site that you need 5 advanced degrees to understand what was written.  ::)
Title: Re: Redirect message when trying to configure GV
Post by: LTN1 on September 01, 2016, 04:13:23 PM
Quote from: videobruce on September 01, 2016, 06:22:33 AM
I did a search and the 1st hits are that "stackoverflow" site that you need 5 advanced degrees to understand what was written.  ::)

I can see where you may need 5 advanced degrees from average institutions to understand some of these things. At the Ivy Leagues, we don't really need more than one degree. In fact, our dropouts like Bill Gates can do fine navigating the complexities that the regular schools would require years of advanced degrees.

But don't hate us because we're smarter (or more arrogant).   :o
Title: Re: Redirect message when trying to configure GV
Post by: videobruce on September 01, 2016, 05:48:35 PM
You completely missed the point. The interconnect between here and GV is broke. Calling for the user to reconfigure API's and on and on is ridiculous. I tried another browser and receive the same result. I can't add GV because the system is broke. And it's not just this situation where it is a problem.

They expect the average Joe, or even the above average Joe to attempt to go thru all of this??:
http://stackoverflow.com/questions/22595174/google-oauth-the-redirect-uri-in-the-request-did-not-match-a-registered-redirec

http://stackoverflow.com/questions/20732266/authenticate-with-google-oauth-2-0-did-not-match-a-registered-redirect-uri
Title: Re: Redirect message when trying to configure GV
Post by: SteveInWA on September 01, 2016, 06:40:07 PM
Instead of trying to sign on to the OBiTALK dashboard by using a Google user ID/password, instead create a unique OBiTALK user ID and password (and keep track of it!!!).

Once you're signed in, then you can configure Google Voice using your Google account's credentials, as long as you are logged into your Google Voice account in another tab on your web browser.

That error message is because Obihai has some sort of OAUTH 2.0 authentication problem with the portion of their website that is trying to use people's Google credentials as a "single sign-on".   If you would like to help get it fixed, you can forward your issue to support@obihai.com instead of admin@obihai.com (the address in your error message is just a canned error message).
Title: Re: Redirect message when trying to configure GV
Post by: videobruce on September 01, 2016, 09:06:38 PM
Thanks for the work around. The message must of been written by M$ like all of thier error messages which makes no sense or are just wrong.
QuoteThat error message is because Obihai has some sort of OAUTH 2.0 authentication problem with the portion of their website that is trying to use people's Google credentials as a "single sign-on".
I guess that is where the five degrees fits in.  ;)
Title: Re: Redirect message when trying to configure GV
Post by: LTN1 on September 02, 2016, 07:03:41 AM
Quote from: videobruce on September 01, 2016, 09:06:38 PM
I guess that is where the five degrees fits in.  ;)

[/quote]

Once again...yes...five degrees from average schools...but Steve is in the Ivy Leagues...he needs no degrees to be equivalent.

Tongue in cheek all the way about the Ivy thing...and no one missed any point thus far...just don't want to reply on the specifics of this issue as I have no control over how OBiTalk does its web site and authentication.
Title: Re: Redirect message when trying to configure GV
Post by: videobruce on September 03, 2016, 05:18:56 AM
Their website problem has been fixed!