34
edits
m (Added link to the Cloud Storage Scopes List page) |
|||
Line 23: | Line 23: | ||
So, it's obvious that KEY is not a secret, and even called "id" in some providers. We also specify a redirect_uri there, which is required to be either <code>https://</code> link, or a <code>http://localhost[:port]</code> one. Response type "code" means that we want to get a code, not the actual access_token. | So, it's obvious that KEY is not a secret, and even called "id" in some providers. We also specify a redirect_uri there, which is required to be either <code>https://</code> link, or a <code>http://localhost[:port]</code> one. Response type "code" means that we want to get a code, not the actual access_token. | ||
When users open such link, they have to auth to the provider first. When they do, they'd see some information about the application and would be given a choice to allow or deny that application access to user's storage. There different "scopes", which could help application to specify what they want to get access to (for example, application could be limited to read/write files only in a special directory). Providers usually show which scopes application wants to use, so we shouldn't ask for everything if we need only a few permissions. | When users open such link, they have to auth to the provider first. When they do, they'd see some information about the application and would be given a choice to allow or deny that application access to user's storage. There different "scopes", which could help application to specify what they want to get access to (for example, application could be limited to read/write files only in a special directory). Providers usually show which scopes application wants to use, so we shouldn't ask for everything if we need only a few permissions ([[Cloud_Storage_Scopes_List|list of scopes used]]). | ||
[[File:Code_Page.png|thumb|200px|https://www.scummvm.org/c/code page]] | [[File:Code_Page.png|thumb|200px|https://www.scummvm.org/c/code page]] |
edits