OAuth requirement for publishable add-ons that only act as clients to Google

35 Views Asked by At

Let's say we're developing an editor add-on (meant for publication) that does not need to interface to third party services (only to a self-developed API server, A). Does A need to implement OAuth i.e. issue tokens and so on, or is it sufficient to use the OpenID token received from Google with ScriptApp.getIdentityToken() as authentication for A (as mentioned at the bottom of [1]) ?

When the users start the plugin, they will anyway be faced with an OAuth consent screen, which mentions the scopes given in the addon's appsscript.json manifest file.

I don't find the requirements listed in the developer guide [1] clear when they mention "non-Google services".

In other words, will the Google security review fail my add-on if my API server A does not implement OAuth?

Thank you for any clarifications.

Edit : I'm not concerned with sensitive scopes.

[1] https://developers.google.com/gsuite/add-ons/how-tos/non-google-services

0

There are 0 best solutions below