OOB Oauth Flow Deprecation and Existing Tokens

[Evan R.]

Hi, 

Per the blog post here and the email sent out to clientId's that had used the method in the past, we understand the OOB flow is being deprecated and will be moving our token process away from that prior to the warning and deadline dates..

However, the messaging is unclear as to if only the retrieval of new tokens using the OOB method will be blocked, or if existing tokens obtained via that method will be invalidated as well.  

That is, if a user has already granted our desktop clientId access and our application stored the offline refreshToken - will that token continue to work past 10/3/22, or will a new token using an alternative flow need to be obtained prior to then to retain access?

Thank you in advance for any clarification you can provide. 

[Google Ads API Forum Advisor]

Hi Evan,

Thank you for bringing this up. You may reach out to GCP support for explanation. With that being said, it appears to me from the post that only  authorization request  will be deprecated, not the refresh token.

Regards,

Aryeh Google Ads API Team

ref:_00D1U1174p._5004Q2aQxMY:ref