Google Voice back as Approved Service Provider!?

<< < (13/15) > >>

mo832:
Quote from: SteveInWA on September 12, 2014, 07:00:41 pm

The configuration process will "see" your logged on Google session, and ask it permission to access your Google account in the future.  You'll see a pop-up window on your Google account asking for you to permit this.  Once you do so, Obihai and Google exchange secure "access tokens", and there will be no future need for the OBi to know your user name or password at all.


This seems to be a little misleading, from what I can tell. I have gone through the prompt to auto-update the firmware, and then I was asked to reauthorize the GV login with the new method. I got all the familiar permission screens, and then my dashboard said I was connected. So I assume I am now registered with the new Oauth system. But in my Obi settings under device configuration/sp and also in expert config/sp settings, it still shows my google user name. In expert the name field is filled but the password is blank. Therefore, it appears that the Obi still "knows" the Google user address, but not the password or any login info. This is OK with me, but still the Obi technically has a record of the user name at least. Is this correct?

SteveInWA:
Yes, you are correct about the user ID.  I've fixed my post; thanks -- I am getting punch drunk from working on thousands of posts over on the GV and Hangouts forums.

Kage:
Exactly how is this working now with Obi website? I've read on other forums that with the latest firmware update one can no longer configure Google Voice locally and that disabling Obi Talk provisioning is not possible.

Why must we go through the obi site to make a GV call and more importantly are they able to keep track of how many calls you make, to whom, and who your providers are? Can't the new OAuth 2.0 protocol exchange be done locally?

Knowing these answers are important since they involve privacy issues. I have always kept Obi Talk provisioning disabled and prefer it that way. As of yet I haven't updated the firmware with my obi100. 

SteveInWA:
Quote from: Kage on September 16, 2014, 01:45:47 pm

Exactly how is this working now with Obi website? I've read on other forums that with the latest firmware update one can no longer configure Google Voice locally and that disabling Obi Talk provisioning is not possible.

Why must we go through the obi site to make a GV call and more importantly are they able to keep track of how many calls you make, to whom, and who your providers are? Can't the new OAuth 2.0 protocol exchange be done locally?

Knowing these answers are important since they involve privacy issues. I have always kept Obi Talk provisioning disabled and prefer it that way. As of yet I haven't updated the firmware with my obi100. 



This has already been explained at great length elsewhere in the forum.  Do some reading and put your tin foil hat in the drawer where it belongs.

Kage:
Quote from: SteveInWA on September 16, 2014, 02:11:10 pm

This has already been explained at great length elsewhere in the forum.  Do some reading and put your tin foil hat in the drawer where it belongs.


After perusing hundreds and hundreds of posts I could not find it, but maybe instead of being snotty you might be helpful and post it for us. Or better yet provide a quick answer. We're all adults. For me it is a serious issue and if it's nothing I'll be more than happy to acknowledge it.

Navigation

[0] Message Index

[#] Next page

[*] Previous page