I write an add-ons, and publish it.
But when the user open that first, it will see:
It show "This app isn't verified", how should i setting my app's configuration to fix it?
This has been addressed here in Requesting verification docs:
Requirements
In order to submit your OAuth client for review and verification, you must:
Own a domain and have verified ownership with Google, and
Have a page describing your app's privacy policy hosted within the domain.
You do not need to publish your app from an account in this domain.
Steps
In the Apps Script editor, select File > Project properties > Scopes. 2. Make a note of all the scopes your script project uses.
Ensure that you have access to the Cloud Platform project for your Apps Script Project. If your project resides in a Team Drive, you must associate it with a new Cloud Platform project.
Access the API Console by selecting Resources > Cloud platform project… In the dialog that opens, click the top link, which is typically something like [Script Name] - project-id-123456789012. This opens your script's Cloud Platform project.
If you can't find the left nav bar, click the menu icon in the top left.
In the nav bar, select APIs & services > Credentials.
On the OAuth consent screen tab, fill in your Privacy policy URL. This URL must be hosted in a domain you own.
On the Credentials tab, make a note of the Client ID for the Apps Script OAuth client.
In the upper-right corner of the API Console, select ⋮ > Project settings.
Make a note of the Project ID for your Cloud project.
File a review request of your project’s OAuth client. You'll need the client and project IDs you noted, as well as your privacy policy URL and the list of scopes your app requires.
Most verification requests receive a response within 24 to 72 hours. When verification of your OAuth client is confirmed, your app is verified.
Related
I write an add-ons, and publish it.
But when the user open that first, it will see:
It show "This app isn't verified", how should i setting my app's configuration to fix it?
This has been addressed here in Requesting verification docs:
Requirements
In order to submit your OAuth client for review and verification, you must:
Own a domain and have verified ownership with Google, and
Have a page describing your app's privacy policy hosted within the domain.
You do not need to publish your app from an account in this domain.
Steps
In the Apps Script editor, select File > Project properties > Scopes. 2. Make a note of all the scopes your script project uses.
Ensure that you have access to the Cloud Platform project for your Apps Script Project. If your project resides in a Team Drive, you must associate it with a new Cloud Platform project.
Access the API Console by selecting Resources > Cloud platform project… In the dialog that opens, click the top link, which is typically something like [Script Name] - project-id-123456789012. This opens your script's Cloud Platform project.
If you can't find the left nav bar, click the menu icon in the top left.
In the nav bar, select APIs & services > Credentials.
On the OAuth consent screen tab, fill in your Privacy policy URL. This URL must be hosted in a domain you own.
On the Credentials tab, make a note of the Client ID for the Apps Script OAuth client.
In the upper-right corner of the API Console, select ⋮ > Project settings.
Make a note of the Project ID for your Cloud project.
File a review request of your project’s OAuth client. You'll need the client and project IDs you noted, as well as your privacy policy URL and the list of scopes your app requires.
Most verification requests receive a response within 24 to 72 hours. When verification of your OAuth client is confirmed, your app is verified.
I write an add-ons, and publish it.
But when the user open that first, it will see:
It show "This app isn't verified", how should i setting my app's configuration to fix it?
This has been addressed here in Requesting verification docs:
Requirements
In order to submit your OAuth client for review and verification, you must:
Own a domain and have verified ownership with Google, and
Have a page describing your app's privacy policy hosted within the domain.
You do not need to publish your app from an account in this domain.
Steps
In the Apps Script editor, select File > Project properties > Scopes. 2. Make a note of all the scopes your script project uses.
Ensure that you have access to the Cloud Platform project for your Apps Script Project. If your project resides in a Team Drive, you must associate it with a new Cloud Platform project.
Access the API Console by selecting Resources > Cloud platform project… In the dialog that opens, click the top link, which is typically something like [Script Name] - project-id-123456789012. This opens your script's Cloud Platform project.
If you can't find the left nav bar, click the menu icon in the top left.
In the nav bar, select APIs & services > Credentials.
On the OAuth consent screen tab, fill in your Privacy policy URL. This URL must be hosted in a domain you own.
On the Credentials tab, make a note of the Client ID for the Apps Script OAuth client.
In the upper-right corner of the API Console, select ⋮ > Project settings.
Make a note of the Project ID for your Cloud project.
File a review request of your project’s OAuth client. You'll need the client and project IDs you noted, as well as your privacy policy URL and the list of scopes your app requires.
Most verification requests receive a response within 24 to 72 hours. When verification of your OAuth client is confirmed, your app is verified.
I'm trying to create a google apps script project where is required to access by anyone (people with google account) and executed by the same user (user accessing the web app). I've published the app as "web app" and it work with the given url.
Since i need to this web app as a web service using ajax, the browser console return an error of unauthorised access (No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'x' is therefore not allowed access.) this doesn't happen if the web app is published as "Executed by my" and "access by anyone, even anonymous"
anyway, i'm following the instructions in Google Sign-In for Websites and it said i need to access in google developer console to get credential for the project but my google apps script are not displayed in the project list.
Open up the script, go to Resources > Developer Console Project > click on the link attached to the script.
I belongs IT Section which provides and distributes Google Apps and its related service in our company.
Our section has disabled Drive SDK in Google Apps admin Console because of our company policy.
However, many developers requested Drive api in our company.
So, we started registering developer's drive application in google apps marketplace to allow it.
After our registration, developers could use drive api.
However, recently our registration process has stuck in uploading on Chrome Web Store.
(*Please take a look at See step 8.)
Strictly speaking, chrome web store publishing status become rejected.
Moreover, we received app removal notification from chromewebstore-dev-support#google.com, like "Chrome Web Store: Removal notification for app name."
But we have no idea why this app has been rejected.
Here is our step we used to do.
In google developers console, I accessed api manager, and make drive api enabled.
Access drive SDK settings to register app icon and open URL, and save it.
*About open URL, we assume intranet FQDN is forbidden, so we set http://www.google.com as open URL.
In OAuth Concent, type service name and save it.
From api manager, enable Google Apps Marketplace SDK.
We set application name, description, register icon, support URL and drive api scope(https://www.googleapis.com/auth/drive) and save it.
Also prepare zip file for Chrome Web Store that includes manifest json and app icon.
*In manifest json, we wrote app name, description, web app URL(we set google sites) and write as domain-installable.
Upload zip file to chrome web store, icon, screeen shot, promotional tile images, set web site(we set google sites.), category and languages.
In the end, set Visibility option as private and everyone at mydomain.
After published both chrome web store and google apps marketplace, access to marketplace to find published app in our domain.
allow access of drive app in marketplace.
*Above processes were executed on September in 2015,
I believe developer console UI has been dramatically changed for now, so these steps might not match current steps.
### Questions ###
Considering above results, I would like to confirm things below.
I would like to confirm our steps above is correct or not for registering drive application in Google App Marketplace.
By referring Both Apps Marketplace Guides and Apps Marketplace Frequently Asked Questions, I could not find detail for specific steps.
I are wondering whether we must obtain or prepare domain for web application and it must be open on the web or not.
Are there any way to register in-house application in google apps marketplace without publishing on the web(wondering can use FQDN or not).
Is it possible to create Google Apps Marketplace App using service account or client application with Drive API?
Thank you in advance.
1. I would like to confirm our steps above is correct or not for registering drive application in Google App Marketplace. By referring Both Apps Marketplace Guides and Apps Marketplace Frequently Asked Questions, I could not find detail for specific steps.
You seem to have done the steps right. But just to be safe, you can check out Publish your App page on the apps marketplace documentation.
Steps to Publish the app
Go to the Chrome Web Store developer dashboard
Upload the zip file
Add a detailed description of your app for the Marketplace listing
Add your screenshot(s) and promotional tiles for the Marketplace isting
Add the URLs for your app's websites
Set the category, region, language(s), and other configuration details
Note: To publish a private, domain-only app, skip the next step and see the instructions below.
To publish a Marketplace app that is only visible within your own domain, do not use the listing review request form. Instead, on the developer dashboard, locate the "Visibility options" section and select "Private / Everyone at yourdomainname.com" before you publish
2. I are wondering whether we must obtain or prepare domain for web application and it must be open on the web or not.
I'm not sure what you mean by this question, but once the domain has been set and app published, the application will appear in the "For [your domain]" section in the Google Apps Marketplace available on admin.google.com
3. Are there any way to register in-house application in google apps marketplace without publishing on the web(wondering can use FQDN or not).
If you mean private company-wide application, I think Google Apps for Work can do this feature (this will incur additional charge to you though)
4. Is it possible to create Google Apps Marketplace App using service account or client application with Drive API?
Yes, Drive API also uses Domain-wide delegation of Authority in which the domain admin can grant 3rd party apps access to user data.
I have multiple Google Drive Apps published that have different client ids. When one Drive App creates a file, I would like to set the permissions on that file to allow the second Drive App access to that file. My use case is that from the first applications ui, I would like to allow the end user to launch the second application. Currently, the user needs to leave the first application and go to the drive ui and use the context menu to select open with.
In Google Drive UI, there is a context menu that says "View authorized apps...". I am basically looking for an API to add an entry to that list.
Thanks.
Jeremy
That is not possible. For security reasons, an app can only be granted authorization to see a file via direct user action: specifically opening the file with that app via open-with or the web or Android file pickers.