r-lib
[Action Required] Migrate your impacted OAuth out-of-band clients to an alternative method before October 3, 2022
Hello Jenny
I am use gargle inside rgoogleads package inside auth function block.
Out-Of-Band (OOB) flow Migration Guide
I have verified oauth client for this package:
And i recived notifycation from Google Developers team "[Action Required] Migrate your impacted OAuth out-of-band clients to an alternative method before October 3, 2022"
Hello Google OAuth Developer,
We're writing to remind you that the OAuth out-of-band (OOB) flow will be deprecated on October 3, 2022, to protect your users from phishing and app impersonation attacks.
Please check our recent blog post about Making Google OAuth interactions safer for more information.
What do I need to do? No action is required on your part as apps using OOB in testing mode will not be affected by this change. However, we strongly recommend migrating to safer methods as these apps will be immediately blocked when switching to in production status.
If you want to publish your app(s) to production, follow these instructions:
Determine your app(s) client type from your Google Cloud project by following the client links below. Follow the migration guide to migrate your app(s) to an alternative method
Yes, it really is true that OOB auth is going away. New clients have not been able to enable OOB for a while now. Existing clients will, in general, stop having access to the OOB flow on October 3. This impacts gargle (and several downstream packages) as well, which is being tracked in #202. However, I believe our client will continue to have OOB auth for a bit longer, due to an extension.
Two things I don't know about your app:
- Is it in testing mode? Vs. production. The text you give above suggests that is true. Maybe because it's only used by your or colleagues? In that case, maybe OOB auth will continue to work. I don't know.
- Do you really need OOB? I.e. do you use your package interactively from RStudio Workbench or similar? If not, then the loss of OOB auth might not affect your actual workflow.
I'm going to call this a duplicate of #202
Before the end of September, I'll be doing a release of gargle (in addition to a hot fix I'm about to do today) that makes a few things around using OOB or avoiding OOB easier. But mostly all I can do in gargle itself is to better document things. That will probably also come with a blog post.