Support GCD impersonation via modified service account file #612
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change allows a service account json file created by a domain admin to be used to access Google Drive for another user under the same domain.
The service account json file must be manually edited to add these two lines:
The scope can be
drive
,drive.file
, ordrive.appdata
. Fordrive.appdata
, the backups will be stored under the special app data folder that isn't usually visible in the Google Drive. It can only be accessed programmatically with the Spaces setappDataFolder
(the default Spaces isdrive
) with the root id ofappDataFolder
.See discussion here: https://forum.duplicacy.com/t/google-drive-drive-appdata-scope-service-account-impersonate/4462