NO JOY Managing Google OAuth clients

[tycho]

OK; a little bit over my head here.

I still use Google Voice in myriad ways, and have done so dating back to using an Obi100. Relevant here, I have an Obi200 running "3.2.2 (Build: 8680EX-arrynrob10)" from obifirmware.com. No issues whatsoever; I used their firmware on my 100, and have been using it on this 200 since ... forever? The Obi200 is connected to my home inside wire and I use that config for outbound calls from my home phones. (Inbound calls to the GV number do not terminate at the Obi; the GV number is pointed to a Callcentric DID that is registered to a different ATA in the house. Don't ask; works great; not going to change any of that).

Long ago, for whatever purpose (maybe to get GV running on a PBX, or on one of the Obi devices with the arrynrob FW), I created a Google Voice-related OAuth 2.0 token. I did that at least 10 years ago -- I found the directions for creating the token in a file I created in 2016.

I just received this email from "[email protected]:

"[Action Advised] Manage your unused OAuth clients and protect your information"​

​

"Hello Google Developer,​

​

In accordance with OAuth 2.0 Policies, the following projects that you manage have OAuth clients that have been inactive for at least 5 months, and will be deleted in 30 days unless you take action:​

​

obi200-tokens​

​

Visit the Google Cloud Console to see the complete list of inactive clients. ​

​

To prevent OAuth clients from being deleted, use them in a Sign-in with Google flow or to exchange a refresh token for an access token. Do this for each client that you want to retain. "​

As I type this, my Obi200 is happily registered to Google Voice on "SP1"

SP1 Service Status

Parameter Name	Value

[td]Status[/td][td]Connected[/td]

I have dial tone, and outbound calls work as usual.

1. Is my OAuth token even being used in this application, with the Obi200 registering to Google Voice as "SP1"?
   
   
2. If not, and I'm no longer using GV on a PBX (as I did for a while but haven't in forever and don't even think I can do that any more), do I even care if the token is deleted?
   
   
3. If the token is being used in the Obi200 registration context (the Obi200 is on, and registering 24/7), why does Google think the token/project I labeled "obi200-tokens" long ago has been "inactive for at least 5 months"?
   
   
4. Other than just using my phone, how do I keep the token for this use case? I do not follow the guidance to "use them in a Sign-in with Google flow or to exchange a refresh token for an access token. Do this for each client that you want to retain." I know nothing about a Google Flow, and am uncertain how to "exchange a refresh token for an access token" in this context, and keep my Obi200 working.

So, looking for a fix to this situation -IF- I actually still need the token for my Obi200 use, and -IF- the "it's unused" claim is real. I'm well aware of all the alternatives to GV, have prepared for its demise lo these many "the GV sky is falling" years, but if I don't have to change things now I'd prefer not to (so recommendations along those lines will be cheerfully ignored).

 

[kenn10]

I got the same email but only have gvoice on my smartphone now. I used to have various accounts connected to IncrediblePBX but dumped them years ago. On my gvoice account I do get constant reminders that I'll lose my number if I don't use it so I make a point to use it at least once a month.

Ride that wave until it crashes. I otherwise have no useful information. I'm guessing the OAuth for the Obi will eventually be invalidated. Google has systematically closed off various access that they no longer want to support.