community
/
rclone
3
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

drive: update Internal OAuth consent screen docs 

Updated instructions in `Making your own client_id` section to record process for selecting "Internal" OAuth consent screen.
This commit is contained in:
Phil Shackleton 2022-06-17 16:50:01 +01:00 committed by GitHub
parent 295006f662
commit 8e2d9a4cb9
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 10 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
docs/content/drive.md
View File

@ -1458,8 +1458,9 @@ enter "Developer Contact Email" (your own email is OK); then click on "Save" (al
Click again on "Credentials" on the left panel to go back to the
"Credentials" screen.
(PS: if you are a GSuite user, you could also select "Internal" instead
of "External" above, but this has not been tested/documented so far).
(PS: if you are a GSuite user, you could also select "Internal" instead
of "External" above, but this will restrict API use to Google Workspace
users in your organisation).
6. Click on the "+ CREATE CREDENTIALS" button at the top of the screen,
then select "OAuth client ID".
@ -1467,14 +1468,18 @@ then select "OAuth client ID".
7. Choose an application type of "Desktop app" and click "Create". (the default name is fine)
8. It will show you a client ID and client secret. Make a note of these.
(If you selected "External" at Step 5 continue to "Publish App" in the Steps 9 and 10.
If you chose "Internal" you don't need to publish and can skip straight to
Step 11.)
9. Go to "Oauth consent screen" and press "Publish App"
10. Provide the noted client ID and client secret to rclone.
11. Click "OAuth consent screen", then click "PUBLISH APP" button and
10. Click "OAuth consent screen", then click "PUBLISH APP" button and
confirm, or add your account under "Test users".
11. Provide the noted client ID and client secret to rclone.
Be aware that, due to the "enhanced security" recently introduced by
Google, you are theoretically expected to "submit your app for verification"
and then wait a few weeks(!) for their response; in practice, you can go right