0
votes

We have an existing web app which uses Google's OAuth 2.0 APIs for Admin Directory, Drive, etc for administrative tasks like backup and audit.

Currently we let our customers install backup and audit independently as 'modules' and each have separate client_ids and separate OAuth scopes (i.e. Admin directory for one, Drive for another).

We want to bring our app to the Google Apps Marketplace, and take advantage of Google Sign In (OpenID Connect), use service accounts with domain-wide delegation of authority, but still let our customers only authorize scopes they want to use.

Can we add new scopes to Google Apps Marketplace apps when a user wants to enable a certain feature?

The best practise guidelines (1) indicate that we should request all scopes we might want up front via the Marketplace SDK scopes section but we want to only request the scopes our customers are going to actually use.

(1) https://developers.google.com/apps-marketplace/practices#1_complete_the_listing_review_request_form

1

1 Answers

1
votes

You can add new scopes. Your customer will still have to grant access though for the new scope/s from the ADMIN console.