Unable to make app internal
Sindre Duedahl
Google Ads API Forum Advisor
Hi Sindre,
Thanks for reaching out to the Google Ads API Forum. I hope you are doing well today.
With regards to your concern about “Setting up your OAuth consent screen”, note that you must configure an OAuth consent screen before using an OAuth 2.0 client ID. This article describes OAuth consent screen settings and their impact on how your Google Cloud Platform project requests OAuth scopes from a Google Account.
The user type setting impacts your app's potential audience.
The “External” user type is available to any user with a Google Account. A user's ability to authorize your app's requested scopes are impacted by your project's publishing status, whether testing or in production.
The “Internal'' user type, configured with projects associated with a Google Cloud Organization and the users to limit authorization requests to members of the organization.
For more information about migrating a project into a Google Cloud Organization resource, see Migrating projects into an organization.
User authorization of scopes associated with restricted Google Workspace services, including high-risk Gmail and Drive scopes, might require additional configuration by your organization's administrators. For more information, see the Let Internal apps access restricted Google Workspace APIs section of the Control which third-party and internal apps access Google Workspace data article.
An org_internal authorization error is displayed when authorization is requested from users outside the Google Cloud project's parent.
That being said from the above information, I recommend creating a Google Workspace account if you want to use the “Internal” user type of OAuth consent screen.
I hope it helps. Have a great day.
Regards,
|
||||||
ref:_00D1U1174p._5004Q2ixwOp:ref