Hi, Per the blog post here <https://developers.googleblog.com/2022/02/making-oauth-flows-safer.html>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 <https://developers.googleblog.com/2022/02/making-oauth-flows-safer.html#instructions-oob> need to be obtained prior to then to retain access? Thank you in advance for any clarification you can provide. -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog: https://googleadsdeveloper.blogspot.com/ =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups "AdWords API and Google Ads API Forum" group. To post to this group, send email to adwords-api@googlegroups.com To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en --- You received this message because you are subscribed to the Google Groups "Google Ads API and AdWords API Forum" group. To unsubscribe from this group and stop receiving emails from it, send an email to adwords-api+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/ddf407ac-1ed0-4d67-9b63-f2bd3a0e3bben%40googlegroups.com.
