What causes the Google Drive app to request permission to "Perform these operations when I’m not using the app",

When creating applications in Google Drive, there are a number of "scopes" that can be specified to tell users what permissions are required to run this application.

One of these permissions:

Perform these operations if I am not using the application.

Of great concern to our users. We could not find a final explanation of what causes this permission.

The only possibility we could think of is that using server-side stream for OAuth2 means that the server can still sync after closing the browser, and therefore this should be noted.

If this is the case, will using JS direct for the drive (without a proxy server) mean that this permission will not be requested?

+1
source share
1 answer

This is due to the OAuth2 flavor of your choice.

You probably used the taste of a web server thread that creates a grant URL with a parameter access_type = offline.

This allows you to get an update token so that you can access your custom files after it has used your application.

access_type paramater access_type=online, . . .

, .

.

+4

All Articles