sounds like we don't need to verify. which is good. i can certainly create (and reauthenticate) desktop apps.
assuming the following: a. accessing 25 accounts nightly b. backend process using ads.properties paradigm via Google's JAVA v11 libs If i do this will the desktop client stop working periodically and require reauthorization or should i expect it to persist forever. thanks On Monday, September 26, 2022 at 12:09:36 PM UTC-7 adsapi wrote: > Hi Lawrence, > > Thanks for getting back to us. > > Kindly note that for the *OAuth2 desktop app flow* > <https://developers.google.com/google-ads/api/docs/oauth/cloud-project#desktop>, > > you can persist a refresh token (which never expires) to obtain a new > access token whenever necessary. When using one of our *client libraries* > <https://developers.google.com/google-ads/api/docs/oauth/client-library>, > you can authorize your app by filling out a configuration file. Since you > are using Java, then you may use our latest client library which already > migrated from OOB to redirect URL, and for local testing that's compatible > with the default configuration in our client library examples, use > *http://127.0.0.1* <http://127.0.0.1/>. You may also add a port number to > your redirect URI to restrict usage to a specific port. If the port is not > set, an OAuth client can redirect to any port. For Desktop app clients, you > will still use a *loopback IP redirect* > <https://developers.google.com/identity/protocols/oauth2/native-app#redirect-uri_loopback>, > > but the URI is not explicitly configured in the Cloud console. > > With regards to verification, our documents says “We recommend that all > apps undergo the Google OAuth verification process as soon as possible to > avoid any business interruptions.” > > > > For information on OAuth Verification, and how to verify your projects, > please refer to the below links: > > - How to verify: OAuth API verification FAQs - Google Cloud Platform > Console Help <https://support.google.com/cloud/answer/9110914> > - General information: Unverified apps - Google Cloud Platform Console > Help <https://support.google.com/cloud/answer/7454865> > > However, if your app is going to be used in any of the following > scenarios, you do not need to submit it for review: > > 1. Personal Use: The app is not shared with anyone else or will be > used by fewer than 100 users (all of whom are known personally to you). > Note that your app will be subject to the unverified app screen and the > 100-user cap will be in effect. > 2. Development/Testing/Staging: If your app’s publishing status is set > to “Testing” and not “In production”, then you do not need to submit your > app for verification. Note that your app will be subject to the unverified > app screen > <https://support.google.com/cloud/answer/7454865#unverified-app-screen> > and the 100-user cap will be in effect. Learn more about Publishing > status <https://support.google.com/cloud/answer/10311615#zippy=>. > 3. Service-owned Data Only: The app only accesses its own data (using > a Service Account), and not user data (linked to a Google Account). > 4. To understand what service accounts are, see Service accounts > <https://cloud.google.com/compute/docs/access/service-accounts>. > 5. For instructions on using a service account, see Using OAuth 2.0 > for Server to Server Applications > <https://developers.google.com/identity/protocols/oauth2/service-account> > . > 6. Internal Use: The app is used only by people in your Google > Workspace or Cloud Identity organization. Note that your app will not be > subject to the unverified app screen or the 100-user cap if it's marked as > Internal. > 7. Learn more about public and internal applications > <https://support.google.com/cloud/answer/6158849#public-and-internal>. > 8. Learn how to mark your app as internal in the FAQ How can I mark my > app as internal-only? > <https://support.google.com/cloud/answer/9110914#mark-internal> > 9. Domain-wide Installation: The app is used only by Google Workspace > enterprise users. Access will depend on permission being granted by the > domain administrator. Google Workspace domain administrators are the only > ones that can add the app to an allowlist for use within their domains. > 10. To learn how to make your app a Domain-Wide Install, see My > application has users with enterprise accounts from another Google > Workspace Domain. > <https://support.google.com/cloud/answer/9110914#enterprise> > 11. SMTP/IMAP/WP: The app is used to send emails through WordPress, or > similar single-account SMTP plugins. > > > > Let us know how this goes on your end. > > Regards, > [image: Google Logo] > Yasar > Google Ads API Team > > > ref:_00D1U1174p._5004Q2efNUO:ref > -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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/ad153463-2031-4fc7-80b8-c81bda2b9a9fn%40googlegroups.com.
