Google has removed clientlogin

[iameli]

Hi,

Looks like googleclientlogin doesn't work anymore. See this Ajnasz/GoogleClientLogin#11

As such, this library isn't able to auth with google.

[Pome-ro]

Oh lame, I just found this library and was looking to play around with it.

[nivoset]

Do we have a work around or a fork that allows the use of a oauth key instead? (and if so, is there a nice walk through on how to make/use it?)

[amper5and]

This change has been anticipated for a VERY LONG time and quite frankly, it's surprising that Google held on to ClientLogin as long as it did. Back in the day, I spent a lot of effort trying to seamlessly build in oauth authentication, but this required reverse engineering the ios app. I almost had something, but it was bloated and buggy, so it was (properly) put on hold. I will swing around to it one of these days and try again, but please feel free to contribute to the project. We should be able to fix something as trivial as a login issue the more minds we put together!

[zalmyr]

@nivoset this work around worked for me see link #21 (comment)

[dwhitacre]

We really should not be using #21 (comment) to work around this issue, especially for deployment. You can use it for testing, but every time you get logged out of google voice you get a new authentication cookies which voids you're old one. So unless you want to have your application just constantly make sure your google voice account is still logged in, this is not a viable solution.

Edit: Turns out your old auth cookies do not get voided. You do get a new one, but the old one has a lifetime of two years. Still not a viable solution though.

[zalmyr]

@dwhitacre I agree that this shouldn't be used in production.

[iameli]

@dwhitacre @zalmyr I hear what you're saying -- on the other hand I'd be skeptical of anything using a totally undocumented unauthorized Google API and calling itself "production".

[ajay-gandhi]

@amper5and I have some time and wouldn't mind trying to incorporate OAuth – any tips on getting started? What did you do that "almost got you something"?

[pixelsage]

Oh darn. Just found this library with excitement until I saw this issue. Sad. I was going to try and make my own Google Voice app with this library =/

[dwhitacre]

@nivoset yea unless somebody implements oauth then its no longer useful. At the same time, I believe google is getting rid of google voice anyways so its really no longer applicable.

[dwhitacre]

@nivoset I was running a server a couple months ago, for my own use, that was using this anyways.. but it crashed and burned from this specific issue after 3 or 4 months

[ericblade]

You can't get access to the voice system from the oauth login according to what I've heard. Technically all of the voice calls are undocumented and unauthorized.

[amper5and]

This was always a risk that I pointed out in the docs. I kinda hoped it
wouldn't happen but as it is we held out for longer than I initially
imagined.

At one point a few years ago I figured out all the calls the Google voice
iOS app made and Mickey moused an oauth version. The app has been updated
many times since then and I haven't gone back to see if the server calls
are identical. It's a huge time investment and at the whim of Google making
a single change in the app that could break it. I'm not too keen on
rewriting the library to use this implementation. I could dig into it again
if there is interest and input from you guys. I'm also open to other ideas.
On Tue, Apr 26, 2016 at 11:18 Eric Blade [email protected] wrote:

You can't get access to the voice system from the oauth login according to
what I've heard. Technically all of the voice calls are undocumented and
unauthorized.

—
You are receiving this because you were mentioned.

Reply to this email directly or view it on GitHub
#23 (comment)

[ericblade]

I'd be willing to put in some time snooping around with it. I have an iPad 2 that I don't use for anything, so could be a candidate for figuring out what it does. I also happen to have a spare Mac that I could use, assuming that these instructions are functional: https://developer.apple.com/library/ios/qa/qa1176/_index.html#//apple_ref/doc/uid/DTS10001707-CH1-SECIOSPACKETTRACING

I also haven't done more than a handful of packet tracing operations in my life, and I've never actually used the Mac for anything other than firing off remote compilation tasks, so following those directions might be easier said than done. ;-)

I find it incredibly interesting that the iOS app has an updated login method that none of the other ways in seem to be using. I wonder if the iOS app just plain has a newer core from it's beginning?

[ericblade]

... just spent a bunch of time nosing around in the official Chrome extension, and see no useful information there. That just uses the _rnr token.

[healer1012]

Hi amper5and
I have just used your library... got a googleclient login issue.(emain and password is correct)

Please let me know how can I fix this issue.

[ericblade]

I may be wrong, but I'm pretty sure that ClientLogin has been dead for 5 years now.

[healer1012]

Thanks for your kind reply. Then which module can I use instead of GoogleClientLogin?
And which part of current code should I change?
If you give me some example or guide then I am very appreciate your help.
Thanks.

[ericblade]

Unfortunately, I've got nothing on that. I've not been able to make this or any other Voice implementation work ever since they overhauled the user interface years ago.