Hi everyone,
I'm writing to you because I have some questions about the application verification for the Google Drive API integration in our SaaS product.
Context
We are creating a Social Intranet as a SaaS product, within which there is a document management system. In it, documents can be uploaded from a computer, but documents can also be linked from Google Drive.
This product is used by multiple customers, so there are different environments with different domain names. Each customer has its own domain or subdomain.
Questions
- If a customer wants to use our Google Drive API implementation, we have to add a domain name to the Authorized JavaScript origins. Do we need to verify the main domain when adding a subdomain? Or can we comply by verifying the subdomain?
- Can we do this process once and then route the traffic through our own domain afterwards. To avoid verification per customer implementation?
- What are other solutions to implement this for multiple customers without the hassle?
I look forward to hearing from you.
LinkedIn
Twitter
